Bug 102569

Summary: [CSS Regions] Setting flow-into to none does not remove element from named flow
Product: WebKit Reporter: Alan Stearns <stearns>
Component: CSSAssignee: Nobody <webkit-unassigned>
Status: RESOLVED INVALID    
Severity: Normal CC: donggwan.kim, mibalan, WebkitBugTracker
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 57312    
Attachments:
Description Flags
Testfile - display should read One Two Three none

Alan Stearns
Reported 2012-11-16 16:08:44 PST
Created attachment 174776 [details] Testfile - display should read One Two Three If you have an element in a named flow, and you add flow-into:none for a child of that element, the child stays in the named flow. If an element's flow-into property computes to none, it should not be included in a named flow.
Attachments
Testfile - display should read One Two Three (478 bytes, text/html)
2012-11-16 16:08 PST, Alan Stearns 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Alan Stearns
Comment 1 2012-11-21 12:04:50 PST
Andrei Bucur pointed out that I was misinterpreting the spec. The flow-into property is not inherited, so all the children of an element moved into a named flow already have flow-into computing to 'none'. So setting this explicitly shouldn't make a difference.
Note You need to log in before you can comment on or make changes to this bug.