Bug 95453

Summary: [CSS Regions] Add test for event firing sequence for regionoversetchange with nested namedflows
Product: WebKit Reporter: Mihai Balan <mibalan>
Component: CSSAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WONTFIX    
Severity: Normal CC: abucur, bfulgham, donggwan.kim, stearns, WebkitBugTracker
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 57312    
Attachments:
Description Flags
Ref test highlighting the problem
none
Ref test highlighting the problem none

Mihai Balan
Reported 2012-08-30 06:50:36 PDT
The CSS Regions spec currently states that "If region chain nesting occurs (the contents of a NamedFlow contains regions for a different NamedFlow) then the regionLayoutUpdate event for the nested flow(s) must be dispatched before the regionLayoutUpdate event for the containing flow is dispatched." However, in the current implementation, first the event for the containing flow is dispatched and then the event for the nested flow.
Attachments
Ref test highlighting the problem (1.85 KB, application/x-zip-compressed)
2012-08-30 06:55 PDT, Mihai Balan 		no flags
Details
Ref test highlighting the problem (1.71 KB, application/x-zip-compressed)
2012-08-31 09:04 PDT, Mihai Balan 		no flags
Details
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Mihai Balan
Comment 1 2012-08-30 06:55:36 PDT
Created attachment 161460 [details] Ref test highlighting the problem
Mihai Balan
Comment 2 2012-08-31 09:04:22 PDT
Created attachment 161711 [details] Ref test highlighting the problem Uploaded new version that doesn't throw JavaScript exceptions in expected file.
Alan Stearns
Comment 3 2013-05-23 09:47:01 PDT
The spec has changed to trigger the events at the end of the visual formatting steps, which run outside-in: http://dev.w3.org/csswg/css-regions/#named-flows-layout So the order is correct at this time. We should add a test for this.
Michelangelo De Simone
Comment 4 2013-06-13 20:25:27 PDT
Still repros on today's nightly (r151543)
Mihai Balan
Comment 5 2013-07-15 22:48:05 PDT
Since the spec doesn't make any specification of event timing for nested regions, this should be closed as soon as we remove the regionlayoutupdate event.
Alan Stearns
Comment 6 2013-07-16 07:16:12 PDT
The spec does say how events in nested regions should trigger. The implementation matches the spec at the moment.
Brent Fulgham
Comment 7 2022-07-12 17:15:34 PDT
CSS Regions were removed in Bug 174978.
Note You need to log in before you can comment on or make changes to this bug.