[Webkit-unassigned] [Bug 87300] New: Add a list of tags (RenderBlocks) that shouldn't run-in
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed May 23 13:08:22 PDT 2012
https://bugs.webkit.org/show_bug.cgi?id=87300
Summary: Add a list of tags (RenderBlocks) that shouldn't
run-in
Product: WebKit
Version: 528+ (Nightly build)
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: Layout and Rendering
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: inferno at chromium.org
CC: inferno at chromium.org
http://www.w3.org/TR/css3-box/#run-in-boxes is pretty vague and does not define which tags should run-in and which shouldn't run-in.
Currently we exclude <select> and <progress> (matches Opera). Firefox does not implement run-in yet. and IE does not support new tags like <progress>. IE and Opera do not allow on <select>
On another bug,
Comment #2 From Darin Adler 2012-05-23 13:01:12 PST (-) [reply]
(From update of attachment 143589 [details])
View in context: https://bugs.webkit.org/attachment.cgi?id=143589&action=review
> Source/WebCore/rendering/RenderBlock.cpp:1850
> if (runInNode && runInNode->hasTagName(selectTag))
> return;
>
> + if (runInNode && runInNode->hasTagName(progressTag))
> + return;
Although this is OK as a “band-aid”, I don’t think a laundry list of specific tags is the way to go here. We need some higher level concept of elements that can’t turn into a run-in rather than a list of tags here. Maybe a virtual function specifically for this in Node, Element, or HTMLElement?
There must be some pattern of which elements this is inappropriate for. Some rule rather than just individual cases. This might even be something that’s addressed by the CSS or HTML specifications, in fact.
Please follow up on this.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list