Closed
Bug 1490022
Opened 7 years ago
Closed 7 years ago
[wpt-sync] Sync PR 12930 - HTML: test fieldset percentage block size
Categories
(Core :: DOM: Core & HTML, enhancement, P4)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla64
| Tracking | Status | |
|---|---|---|
| firefox64 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 12930 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/12930
Details from upstream follow.
Simon Pieters <zcorpan@gmail.com> wrote:
> HTML: test fieldset percentage block size
>
> See https://github.com/whatwg/html/pull/3934
| Assignee | ||
Updated•7 years ago
|
Component: web-platform-tests → DOM
Product: Testing → Core
| Assignee | ||
Comment 1•7 years ago
|
||
| Assignee | ||
Comment 2•7 years ago
|
||
| Assignee | ||
Comment 3•7 years ago
|
||
| Assignee | ||
Comment 4•7 years ago
|
||
Ran 1 tests and 9 subtests
OK : 1
PASS : 3
FAIL : 6
New tests that have failures or other problems:
/html/rendering/non-replaced-elements/the-fieldset-and-legend-elements/fieldset-percentage-block-size.html
div (writing-mode: horizontal-tb): FAIL
div (writing-mode: vertical-lr): FAIL
div (writing-mode: vertical-rl): FAIL
second legend (writing-mode: horizontal-tb): FAIL
second legend (writing-mode: vertical-lr): FAIL
second legend (writing-mode: vertical-rl): FAIL
| Assignee | ||
Comment 5•7 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=8c66def537f1ac5ffd94285b76ae5cbab7e29f96
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/bef432676695
[wpt PR 12930] - HTML: test fieldset percentage block size, a=testonly
Comment 7•7 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox64:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
Updated•7 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•