Skip to main content

Browse the archive

Revision 5e78f769b58842d55ff8d2dc961d9db5a81f769a authored by Eric Willigers on 04 July 2018, 04:36:49 UTC, committed by Eric Willigers on 04 September 2018, 21:58:33 UTC 
[css-grid]  Parse various grid properties
 
Spec: https://drafts.csswg.org/css-grid/

These tests highlight the following 5 issues:

Spec
[cssom] [css-grid] Serialization of custom identifiers
https://github.com/w3c/csswg-drafts/issues/2858

Spec
[css-grid] grid-line custom identifier auto?
https://github.com/w3c/csswg-drafts/issues/2856

Edge
grid-area should reject non-integer numbers
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/18112694/

Firefox
grid-auto-columns/rows should accept multiple track-size values
https://bugzilla.mozilla.org/show_bug.cgi?id=1339672

WebKit
[CSS Grid Layout] Fix grid-{row, column, area} shorthand CSSOM serialization
https://bugs.webkit.org/show_bug.cgi?id=149890

Note that some properties such as grid and grid-template are not yet tested.
1 parent 61bc4ec
Raw File
sync-no-timeout.any.js 
// META: global=sharedworker
// META: timeout=long

// This is a regression test for https://crbug.com/844268, when a timeout of 10
// seconds was applied to XHR in Chrome. There should be no timeout unless the
// "timeout" parameter is set on the object.
test(t => {
  let xhr = new XMLHttpRequest();

  // For practical reasons, we can't wait forever. 12 seconds is long enough to
  // reliably reproduce the bug in Chrome.
  xhr.open('GET', 'resources/trickle.py?ms=1000&count=12', false);

  // The test will fail if this throws.
  xhr.send();
}, 'Sync XHR should not have a timeout');
back to top