Bug 102569 - [CSS Regions] Setting flow-into to none does not remove element from named flow
Summary: [CSS Regions] Setting flow-into to none does not remove element from named flow
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 57312
  Show dependency tree / graph
 
Reported: 2012-11-16 16:08 PST by Alan Stearns
Modified: 2012-11-21 12:04 PST (History)
3 users (show)

See Also:

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 an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alan Stearns 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.
Comment 1 Alan Stearns 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.