Revision 87bec7f2841f42f6738d11db4e7986fa95e63ea2 authored by Sergio Villar Senin on 23 March 2018, 11:33:30 UTC, committed by Chromium WPT Sync on 23 March 2018, 11:33:30 UTC
Indefinitely sized containers use the specified definite min-size (if any) as
available space in order to compute the number of auto repeat tracks to
create. A bug in that code was causing the grid to be one track larger than
expected. That was only happening in the case of the free space being
a multiple of the total size of the autorepeat tracks.
Bug: 823140
Change-Id: I6cc13df478da4ba00585fa557012391291941d1a
Reviewed-on: https://chromium-review.googlesource.com/973522
Commit-Queue: Sergio Villar <svillar@igalia.com>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Reviewed-by: Manuel Rego Casasnovas <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#545403}
1 parent b04a923
README.md
Tests for the [Files and Directory Entries API](https://github.com/wicg/entries-api)
* [Explainer](https://github.com/WICG/entries-api/blob/gh-pages/EXPLAINER.md)
* [Draft Specification](https://wicg.github.io/entries-api/)
Unfortunately, most of the tests are **manual** and require drag-and-drop of test
data files, which can be found in the `entries-api/support` directory. The tests
can be run via [w3c-test.org](http://w3c-test.org/entries-api/), but a local clone
of the repo is required for access to the test data files.
Computing file changes ...
