Closed Bug 1499692 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 13566 - Fix a test with missing period after <strong>no red</strong>

Categories

(Core :: CSS Parsing and Computation, enhancement, P4)

Product:
Core
Component:
CSS Parsing and Computation
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla65
Tracking Flags:
Tracking Status
firefox65 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream]) 

Sync web-platform-tests PR 13566 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/13566
Details from upstream follow.

Philip Jägenstedt <philip@foolip.org> wrote:
>  Fix a test with missing period after <strong>no red</strong>
>  
>  That test is border-top-width-003.xht, discovered here:
>  https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://taskcluster-artifacts.net/U6OIGr7ZTjurDYjy_KgyCg/0/public/results/log_tbpl.log
>  
>  default-attribute-selector-*.xht are visual tests, but change them
>  anyway for consistency with other tests to avoid confusion if anyone
>  tries to convert them to reftests.
Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Ran 1 tests
PASS   : 1[linux32-debug,linux64-debug,linux64-opt]

Tests that are disabled for instability:
/css/CSS2/borders/border-top-width-003.xht: [linux32-opt]
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/474f3a9bc7a6
[wpt PR 13566] - Fix a test with missing period after <strong>no red</strong>, a=testonly
https://hg.mozilla.org/integration/mozilla-inbound/rev/504434107342
[wpt PR 13566] - Update wpt metadata, a=testonly
https://hg.mozilla.org/mozilla-central/rev/474f3a9bc7a6
https://hg.mozilla.org/mozilla-central/rev/504434107342
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox65: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla65
You need to log in before you can comment on or make changes to this bug.