[css-tables] Change specificity in harmonization of collapsed borders? · Issue #606 · w3c/csswg-drafts (original) (raw)
Comments
[css-tables] harminozation of collapsed borders [css-tables] Change specificity in harmonization of collapsed borders?
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this issue
This CL contains tests only, no behavior change.
Chrome passes 001. Firefox passes 001 and 002. Safari hidpi passes 001, 002, and 003.
Chrome probably passes 001 but fails 002 because of LayoutUnit's 1/64 pixel precision but that's not confirmed.
Note that these tests will become invalid if the proposal in w3c/csswg-drafts#606 is adopted.
Bug: 377847 Change-Id: Ifc9e8f9f878f7462cb949670350eadb17c7c2940
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this issue
This CL contains tests only, no behavior change.
Chrome passes 001. Firefox passes 001 and 002. Safari hidpi passes 001, 002, and 003.
Chrome probably passes 001 but fails 002 because of LayoutUnit's 1/64 pixel precision but that's not confirmed.
Note that these tests will become invalid if the proposal in w3c/csswg-drafts#606 is adopted.
Bug: 377847 Change-Id: Ifc9e8f9f878f7462cb949670350eadb17c7c2940
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this issue
This CL contains tests only, no behavior change.
Chrome passes 001. Firefox passes 001 and 002. Safari hidpi passes 001, 002, and 003.
Chrome probably passes 001 but fails 002 because of LayoutUnit's 1/64 pixel precision but that's not confirmed.
Note that these tests will become invalid if the proposal in w3c/csswg-drafts#606 is adopted.
Bug: 377847 Change-Id: Ifc9e8f9f878f7462cb949670350eadb17c7c2940
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this issue
This CL contains tests only, no behavior change.
Chrome passes 001. Safari lodpi and Firefox pass 001 and 002. EdgeHTML 18.17763 and Safari hidpi pass 001, 002, and 003.
Chrome probably passes 001 but fails 002 because of LayoutUnit's 1/64 pixel precision but that's not confirmed.
Note that these tests will become invalid if the proposal in w3c/csswg-drafts#606 is adopted.
Bug: 377847 Change-Id: Ifc9e8f9f878f7462cb949670350eadb17c7c2940
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this issue
This CL contains tests only, no behavior change.
Chrome passes only 001, no matter the device pixels. Safari-lodpi and Firefox-lodpi pass only 001 and 002. EdgeHTML 18.17763-lodpi, Firefox-hidpi, and Safari-hidpi pass 001, 002, and 003.
From a plain reading of the tables spec the 003 test is correct. But given its rampant failure (only EdgeHTML passes when 1x device pixel per CSS pixel), it'd be reasonable to codify the current empirical behavior somewhere, if it's not already in a place that I missed.
Chrome probably passes 001 but fails 002 because of LayoutUnit's 1/64 pixel precision but that's not confirmed.
Note that these tests will become invalid if the proposal in w3c/csswg-drafts#606 is adopted.
Bug: 377847 Change-Id: Ifc9e8f9f878f7462cb949670350eadb17c7c2940
aarongable pushed a commit to chromium/chromium that referenced this issue
This CL contains tests only, no behavior change.
Chrome passes only 001, no matter the device pixels. Safari-lodpi and Firefox-lodpi pass only 001 and 002. EdgeHTML 18.17763-lodpi, Firefox-hidpi, and Safari-hidpi pass 001, 002, and 003.
From a plain reading of the tables spec the 003 test is correct. But given its rampant failure (only EdgeHTML passes when 1x device pixel per CSS pixel), it'd be reasonable to codify the current empirical behavior somewhere, if it's not already in a place that I missed.
Chrome probably passes 001 but fails 002 because of LayoutUnit's 1/64 pixel precision but that's not confirmed.
Note that these tests will become invalid if the proposal in w3c/csswg-drafts#606 is adopted.
Bug: 377847 Change-Id: Ifc9e8f9f878f7462cb949670350eadb17c7c2940 Reviewed-on: https://chromium-review.googlesource.com/c/1477334 Reviewed-by: Morten Stenshorne mstensho@chromium.org Reviewed-by: David Grogan dgrogan@chromium.org Commit-Queue: David Grogan dgrogan@chromium.org Cr-Commit-Position: refs/heads/master@{#633538}
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this issue
This CL contains tests only, no behavior change.
Chrome passes only 001, no matter the device pixels. Safari-lodpi and Firefox-lodpi pass only 001 and 002. EdgeHTML 18.17763-lodpi, Firefox-hidpi, and Safari-hidpi pass 001, 002, and 003.
From a plain reading of the tables spec the 003 test is correct. But given its rampant failure (only EdgeHTML passes when 1x device pixel per CSS pixel), it'd be reasonable to codify the current empirical behavior somewhere, if it's not already in a place that I missed.
Chrome probably passes 001 but fails 002 because of LayoutUnit's 1/64 pixel precision but that's not confirmed.
Note that these tests will become invalid if the proposal in w3c/csswg-drafts#606 is adopted.
Bug: 377847 Change-Id: Ifc9e8f9f878f7462cb949670350eadb17c7c2940 Reviewed-on: https://chromium-review.googlesource.com/c/1477334 Reviewed-by: Morten Stenshorne mstensho@chromium.org Reviewed-by: David Grogan dgrogan@chromium.org Commit-Queue: David Grogan dgrogan@chromium.org Cr-Commit-Position: refs/heads/master@{#633538}
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this issue
This CL contains tests only, no behavior change.
Chrome passes only 001, no matter the device pixels. Safari-lodpi and Firefox-lodpi pass only 001 and 002. EdgeHTML 18.17763-lodpi, Firefox-hidpi, and Safari-hidpi pass 001, 002, and 003.
From a plain reading of the tables spec the 003 test is correct. But given its rampant failure (only EdgeHTML passes when 1x device pixel per CSS pixel), it'd be reasonable to codify the current empirical behavior somewhere, if it's not already in a place that I missed.
Chrome probably passes 001 but fails 002 because of LayoutUnit's 1/64 pixel precision but that's not confirmed.
Note that these tests will become invalid if the proposal in w3c/csswg-drafts#606 is adopted.
Bug: 377847 Change-Id: Ifc9e8f9f878f7462cb949670350eadb17c7c2940 Reviewed-on: https://chromium-review.googlesource.com/c/1477334 Reviewed-by: Morten Stenshorne mstensho@chromium.org Reviewed-by: David Grogan dgrogan@chromium.org Commit-Queue: David Grogan dgrogan@chromium.org Cr-Commit-Position: refs/heads/master@{#633538}
moz-v2v-gh pushed a commit to mozilla/gecko-dev that referenced this issue
… border tests, a=testonly
Automatic update from web-platform-tests [css-tables] Add some subpixel collapsed border tests
This CL contains tests only, no behavior change.
Chrome passes only 001, no matter the device pixels. Safari-lodpi and Firefox-lodpi pass only 001 and 002. EdgeHTML 18.17763-lodpi, Firefox-hidpi, and Safari-hidpi pass 001, 002, and 003.
From a plain reading of the tables spec the 003 test is correct. But given its rampant failure (only EdgeHTML passes when 1x device pixel per CSS pixel), it'd be reasonable to codify the current empirical behavior somewhere, if it's not already in a place that I missed.
Chrome probably passes 001 but fails 002 because of LayoutUnit's 1/64 pixel precision but that's not confirmed.
Note that these tests will become invalid if the proposal in w3c/csswg-drafts#606 is adopted.
Bug: 377847 Change-Id: Ifc9e8f9f878f7462cb949670350eadb17c7c2940 Reviewed-on: https://chromium-review.googlesource.com/c/1477334 Reviewed-by: Morten Stenshorne mstensho@chromium.org Reviewed-by: David Grogan dgrogan@chromium.org Commit-Queue: David Grogan dgrogan@chromium.org Cr-Commit-Position: refs/heads/master@{#633538}
--
wpt-commits: 41a8506f54e688d655e662f59584dcbf777990f2 wpt-pr: 15449
mykmelez pushed a commit to mykmelez/gecko that referenced this issue
… border tests, a=testonly
Automatic update from web-platform-tests [css-tables] Add some subpixel collapsed border tests
This CL contains tests only, no behavior change.
Chrome passes only 001, no matter the device pixels. Safari-lodpi and Firefox-lodpi pass only 001 and 002. EdgeHTML 18.17763-lodpi, Firefox-hidpi, and Safari-hidpi pass 001, 002, and 003.
From a plain reading of the tables spec the 003 test is correct. But given its rampant failure (only EdgeHTML passes when 1x device pixel per CSS pixel), it'd be reasonable to codify the current empirical behavior somewhere, if it's not already in a place that I missed.
Chrome probably passes 001 but fails 002 because of LayoutUnit's 1/64 pixel precision but that's not confirmed.
Note that these tests will become invalid if the proposal in w3c/csswg-drafts#606 is adopted.
Bug: 377847 Change-Id: Ifc9e8f9f878f7462cb949670350eadb17c7c2940 Reviewed-on: https://chromium-review.googlesource.com/c/1477334 Reviewed-by: Morten Stenshorne mstensho@chromium.org Reviewed-by: David Grogan dgrogan@chromium.org Commit-Queue: David Grogan dgrogan@chromium.org Cr-Commit-Position: refs/heads/master@{#633538}
--
wpt-commits: 41a8506f54e688d655e662f59584dcbf777990f2 wpt-pr: 15449
moz-v2v-gh pushed a commit to mozilla/gecko-dev that referenced this issue
… border tests, a=testonly
Automatic update from web-platform-tests [css-tables] Add some subpixel collapsed border tests
This CL contains tests only, no behavior change.
Chrome passes only 001, no matter the device pixels. Safari-lodpi and Firefox-lodpi pass only 001 and 002. EdgeHTML 18.17763-lodpi, Firefox-hidpi, and Safari-hidpi pass 001, 002, and 003.
From a plain reading of the tables spec the 003 test is correct. But given its rampant failure (only EdgeHTML passes when 1x device pixel per CSS pixel), it'd be reasonable to codify the current empirical behavior somewhere, if it's not already in a place that I missed.
Chrome probably passes 001 but fails 002 because of LayoutUnit's 1/64 pixel precision but that's not confirmed.
Note that these tests will become invalid if the proposal in w3c/csswg-drafts#606 is adopted.
Bug: 377847 Change-Id: Ifc9e8f9f878f7462cb949670350eadb17c7c2940 Reviewed-on: https://chromium-review.googlesource.com/c/1477334 Reviewed-by: Morten Stenshorne mstensho@chromium.org Reviewed-by: David Grogan dgrogan@chromium.org Commit-Queue: David Grogan dgrogan@chromium.org Cr-Commit-Position: refs/heads/master@{#633538}
--
wpt-commits: 41a8506f54e688d655e662f59584dcbf777990f2 wpt-pr: 15449
mykmelez pushed a commit to mykmelez/gecko that referenced this issue
… border tests, a=testonly
Automatic update from web-platform-tests [css-tables] Add some subpixel collapsed border tests
This CL contains tests only, no behavior change.
Chrome passes only 001, no matter the device pixels. Safari-lodpi and Firefox-lodpi pass only 001 and 002. EdgeHTML 18.17763-lodpi, Firefox-hidpi, and Safari-hidpi pass 001, 002, and 003.
From a plain reading of the tables spec the 003 test is correct. But given its rampant failure (only EdgeHTML passes when 1x device pixel per CSS pixel), it'd be reasonable to codify the current empirical behavior somewhere, if it's not already in a place that I missed.
Chrome probably passes 001 but fails 002 because of LayoutUnit's 1/64 pixel precision but that's not confirmed.
Note that these tests will become invalid if the proposal in w3c/csswg-drafts#606 is adopted.
Bug: 377847 Change-Id: Ifc9e8f9f878f7462cb949670350eadb17c7c2940 Reviewed-on: https://chromium-review.googlesource.com/c/1477334 Reviewed-by: Morten Stenshorne mstensho@chromium.org Reviewed-by: David Grogan dgrogan@chromium.org Commit-Queue: David Grogan dgrogan@chromium.org Cr-Commit-Position: refs/heads/master@{#633538}
--
wpt-commits: 41a8506f54e688d655e662f59584dcbf777990f2 wpt-pr: 15449
marcoscaceres pushed a commit to web-platform-tests/wpt that referenced this issue
This CL contains tests only, no behavior change.
Chrome passes only 001, no matter the device pixels. Safari-lodpi and Firefox-lodpi pass only 001 and 002. EdgeHTML 18.17763-lodpi, Firefox-hidpi, and Safari-hidpi pass 001, 002, and 003.
From a plain reading of the tables spec the 003 test is correct. But given its rampant failure (only EdgeHTML passes when 1x device pixel per CSS pixel), it'd be reasonable to codify the current empirical behavior somewhere, if it's not already in a place that I missed.
Chrome probably passes 001 but fails 002 because of LayoutUnit's 1/64 pixel precision but that's not confirmed.
Note that these tests will become invalid if the proposal in w3c/csswg-drafts#606 is adopted.
Bug: 377847 Change-Id: Ifc9e8f9f878f7462cb949670350eadb17c7c2940 Reviewed-on: https://chromium-review.googlesource.com/c/1477334 Reviewed-by: Morten Stenshorne mstensho@chromium.org Reviewed-by: David Grogan dgrogan@chromium.org Commit-Queue: David Grogan dgrogan@chromium.org Cr-Commit-Position: refs/heads/master@{#633538}
gecko-dev-updater pushed a commit to marco-c/gecko-dev-comments-removed that referenced this issue
… border tests, a=testonly
Automatic update from web-platform-tests [css-tables] Add some subpixel collapsed border tests
This CL contains tests only, no behavior change.
Chrome passes only 001, no matter the device pixels. Safari-lodpi and Firefox-lodpi pass only 001 and 002. EdgeHTML 18.17763-lodpi, Firefox-hidpi, and Safari-hidpi pass 001, 002, and 003.
From a plain reading of the tables spec the 003 test is correct. But given its rampant failure (only EdgeHTML passes when 1x device pixel per CSS pixel), it'd be reasonable to codify the current empirical behavior somewhere, if it's not already in a place that I missed.
Chrome probably passes 001 but fails 002 because of LayoutUnit's 1/64 pixel precision but that's not confirmed.
Note that these tests will become invalid if the proposal in w3c/csswg-drafts#606 is adopted.
Bug: 377847 Change-Id: Ifc9e8f9f878f7462cb949670350eadb17c7c2940 Reviewed-on: https://chromium-review.googlesource.com/c/1477334 Reviewed-by: Morten Stenshorne <mstenshochromium.org> Reviewed-by: David Grogan <dgroganchromium.org> Commit-Queue: David Grogan <dgroganchromium.org> Cr-Commit-Position: refs/heads/master{#633538}
--
wpt-commits: 41a8506f54e688d655e662f59584dcbf777990f2 wpt-pr: 15449
UltraBlame original commit: 7d54ecab8dc11d9fc32dc17488dd41e6ca3f170b
gecko-dev-updater pushed a commit to marco-c/gecko-dev-comments-removed that referenced this issue
… border tests, a=testonly
Automatic update from web-platform-tests [css-tables] Add some subpixel collapsed border tests
This CL contains tests only, no behavior change.
Chrome passes only 001, no matter the device pixels. Safari-lodpi and Firefox-lodpi pass only 001 and 002. EdgeHTML 18.17763-lodpi, Firefox-hidpi, and Safari-hidpi pass 001, 002, and 003.
From a plain reading of the tables spec the 003 test is correct. But given its rampant failure (only EdgeHTML passes when 1x device pixel per CSS pixel), it'd be reasonable to codify the current empirical behavior somewhere, if it's not already in a place that I missed.
Chrome probably passes 001 but fails 002 because of LayoutUnit's 1/64 pixel precision but that's not confirmed.
Note that these tests will become invalid if the proposal in w3c/csswg-drafts#606 is adopted.
Bug: 377847 Change-Id: Ifc9e8f9f878f7462cb949670350eadb17c7c2940 Reviewed-on: https://chromium-review.googlesource.com/c/1477334 Reviewed-by: Morten Stenshorne <mstenshochromium.org> Reviewed-by: David Grogan <dgroganchromium.org> Commit-Queue: David Grogan <dgroganchromium.org> Cr-Commit-Position: refs/heads/master{#633538}
--
wpt-commits: 41a8506f54e688d655e662f59584dcbf777990f2 wpt-pr: 15449
UltraBlame original commit: 3a39e45af185cdada307e0e2b4d161928d980817
gecko-dev-updater pushed a commit to marco-c/gecko-dev-wordified that referenced this issue
… border tests, a=testonly
Automatic update from web-platform-tests [css-tables] Add some subpixel collapsed border tests
This CL contains tests only, no behavior change.
Chrome passes only 001, no matter the device pixels. Safari-lodpi and Firefox-lodpi pass only 001 and 002. EdgeHTML 18.17763-lodpi, Firefox-hidpi, and Safari-hidpi pass 001, 002, and 003.
From a plain reading of the tables spec the 003 test is correct. But given its rampant failure (only EdgeHTML passes when 1x device pixel per CSS pixel), it'd be reasonable to codify the current empirical behavior somewhere, if it's not already in a place that I missed.
Chrome probably passes 001 but fails 002 because of LayoutUnit's 1/64 pixel precision but that's not confirmed.
Note that these tests will become invalid if the proposal in w3c/csswg-drafts#606 is adopted.
Bug: 377847 Change-Id: Ifc9e8f9f878f7462cb949670350eadb17c7c2940 Reviewed-on: https://chromium-review.googlesource.com/c/1477334 Reviewed-by: Morten Stenshorne <mstenshochromium.org> Reviewed-by: David Grogan <dgroganchromium.org> Commit-Queue: David Grogan <dgroganchromium.org> Cr-Commit-Position: refs/heads/master{#633538}
--
wpt-commits: 41a8506f54e688d655e662f59584dcbf777990f2 wpt-pr: 15449
UltraBlame original commit: 7d54ecab8dc11d9fc32dc17488dd41e6ca3f170b
gecko-dev-updater pushed a commit to marco-c/gecko-dev-wordified that referenced this issue
… border tests, a=testonly
Automatic update from web-platform-tests [css-tables] Add some subpixel collapsed border tests
This CL contains tests only, no behavior change.
Chrome passes only 001, no matter the device pixels. Safari-lodpi and Firefox-lodpi pass only 001 and 002. EdgeHTML 18.17763-lodpi, Firefox-hidpi, and Safari-hidpi pass 001, 002, and 003.
From a plain reading of the tables spec the 003 test is correct. But given its rampant failure (only EdgeHTML passes when 1x device pixel per CSS pixel), it'd be reasonable to codify the current empirical behavior somewhere, if it's not already in a place that I missed.
Chrome probably passes 001 but fails 002 because of LayoutUnit's 1/64 pixel precision but that's not confirmed.
Note that these tests will become invalid if the proposal in w3c/csswg-drafts#606 is adopted.
Bug: 377847 Change-Id: Ifc9e8f9f878f7462cb949670350eadb17c7c2940 Reviewed-on: https://chromium-review.googlesource.com/c/1477334 Reviewed-by: Morten Stenshorne <mstenshochromium.org> Reviewed-by: David Grogan <dgroganchromium.org> Commit-Queue: David Grogan <dgroganchromium.org> Cr-Commit-Position: refs/heads/master{#633538}
--
wpt-commits: 41a8506f54e688d655e662f59584dcbf777990f2 wpt-pr: 15449
UltraBlame original commit: 3a39e45af185cdada307e0e2b4d161928d980817
gecko-dev-updater pushed a commit to marco-c/gecko-dev-wordified-and-comments-removed that referenced this issue
… border tests, a=testonly
Automatic update from web-platform-tests [css-tables] Add some subpixel collapsed border tests
This CL contains tests only, no behavior change.
Chrome passes only 001, no matter the device pixels. Safari-lodpi and Firefox-lodpi pass only 001 and 002. EdgeHTML 18.17763-lodpi, Firefox-hidpi, and Safari-hidpi pass 001, 002, and 003.
From a plain reading of the tables spec the 003 test is correct. But given its rampant failure (only EdgeHTML passes when 1x device pixel per CSS pixel), it'd be reasonable to codify the current empirical behavior somewhere, if it's not already in a place that I missed.
Chrome probably passes 001 but fails 002 because of LayoutUnit's 1/64 pixel precision but that's not confirmed.
Note that these tests will become invalid if the proposal in w3c/csswg-drafts#606 is adopted.
Bug: 377847 Change-Id: Ifc9e8f9f878f7462cb949670350eadb17c7c2940 Reviewed-on: https://chromium-review.googlesource.com/c/1477334 Reviewed-by: Morten Stenshorne <mstenshochromium.org> Reviewed-by: David Grogan <dgroganchromium.org> Commit-Queue: David Grogan <dgroganchromium.org> Cr-Commit-Position: refs/heads/master{#633538}
--
wpt-commits: 41a8506f54e688d655e662f59584dcbf777990f2 wpt-pr: 15449
UltraBlame original commit: 7d54ecab8dc11d9fc32dc17488dd41e6ca3f170b
gecko-dev-updater pushed a commit to marco-c/gecko-dev-wordified-and-comments-removed that referenced this issue
… border tests, a=testonly
Automatic update from web-platform-tests [css-tables] Add some subpixel collapsed border tests
This CL contains tests only, no behavior change.
Chrome passes only 001, no matter the device pixels. Safari-lodpi and Firefox-lodpi pass only 001 and 002. EdgeHTML 18.17763-lodpi, Firefox-hidpi, and Safari-hidpi pass 001, 002, and 003.
From a plain reading of the tables spec the 003 test is correct. But given its rampant failure (only EdgeHTML passes when 1x device pixel per CSS pixel), it'd be reasonable to codify the current empirical behavior somewhere, if it's not already in a place that I missed.
Chrome probably passes 001 but fails 002 because of LayoutUnit's 1/64 pixel precision but that's not confirmed.
Note that these tests will become invalid if the proposal in w3c/csswg-drafts#606 is adopted.
Bug: 377847 Change-Id: Ifc9e8f9f878f7462cb949670350eadb17c7c2940 Reviewed-on: https://chromium-review.googlesource.com/c/1477334 Reviewed-by: Morten Stenshorne <mstenshochromium.org> Reviewed-by: David Grogan <dgroganchromium.org> Commit-Queue: David Grogan <dgroganchromium.org> Cr-Commit-Position: refs/heads/master{#633538}
--
wpt-commits: 41a8506f54e688d655e662f59584dcbf777990f2 wpt-pr: 15449
UltraBlame original commit: 3a39e45af185cdada307e0e2b4d161928d980817