Bug 172718
| Summary: | legend should only create a block formatting context if it is the "rendered legend" | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Simon Pieters (:zcorpan) <zcorpan> |
| Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | ahmad.saleem792, bfulgham, simon.fraser, zalan |
| Priority: | P2 | Keywords: | FromImplementor, WPTImpact |
| Version: | Safari Technology Preview | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://wpt.fyi/results/html/rendering/non-replaced-elements/the-fieldset-and-legend-elements/legend.html?label=master&label=experimental&aligned&view=subtest&q=legend.html | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=323711 | ||
Simon Pieters (:zcorpan)
<legend> in WebKit avoids floats but otherwise does not create a block formatting context (like in Chromium). This is weird, and not a behavior supported by CSS, and is not interoperable with Gecko or EdgeHTML. The proposal is to make only the "rendered legend" (https://html.spec.whatwg.org/#rendered-legend ) create an actual block formatting context, to make <legend> in general have less magic.
This issue in Chromium:
https://bugs.chromium.org/p/chromium/issues/detail?id=727378
Discussion:
https://github.com/whatwg/html/issues/2519
Proposed spec change:
https://github.com/whatwg/html/pull/2718
In-progress CL for Chromium:
https://chromium-review.googlesource.com/c/512824/
web-platform-tests: none yet
Please raise any concerns in https://github.com/whatwg/html/issues/2519
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Ahmad Saleem
Fixed in - https://chromium-review.googlesource.com/c/chromium/src/+/535595
Ahmad Saleem
* Subtests:
in-body: width
in-fieldset-second-child: width
in-fieldset-descendant: width