A legend with display:contents is not a rendered legend |
|||
Issue descriptionThe CSS Display spec for display:contents says the legend is not a rendered legend and responds normally to display:contents as any other element. Attached test passes on WebKit trunk.
,
Dec 19 2017
,
Dec 19 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/34f26f3449a4cf754afd750db3cacc48c03a3dcd commit 34f26f3449a4cf754afd750db3cacc48c03a3dcd Author: Rune Lillesveen <futhark@chromium.org> Date: Tue Dec 19 10:50:03 2017 Don't force block for display:contents legend. A legend with display:contents is not a rendered legend. See: https://html.spec.whatwg.org/multipage/rendering.html#rendered-legend This fixes a wpt test for display:contents. Bug: 795219 Change-Id: Ib23e7da0491e36c3f4880eaac3c9d704a6730cc3 Reviewed-on: https://chromium-review.googlesource.com/832458 Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#524993} [modify] https://crrev.com/34f26f3449a4cf754afd750db3cacc48c03a3dcd/third_party/WebKit/LayoutTests/TestExpectations [modify] https://crrev.com/34f26f3449a4cf754afd750db3cacc48c03a3dcd/third_party/WebKit/Source/core/css/resolver/StyleAdjuster.cpp
,
Dec 19 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Dec 15 2017