Bug 95453 - [CSS Regions] Add test for event firing sequence for regionoversetchange with nested namedflows
Summary: [CSS Regions] Add test for event firing sequence for regionoversetchange with...
Status: NEW
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 treegraph
 
Reported: 2012-08-30 06:50 PDT by Mihai Balan
Modified: 2013-07-18 07:40 PDT (History)
4 users (show)

See Also:


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

Note You need to log in before you can comment on or make changes to this bug.
Description Mihai Balan 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.
Comment 1 Mihai Balan 2012-08-30 06:55:36 PDT
Created attachment 161460 [details]
Ref test highlighting the problem
Comment 2 Mihai Balan 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.
Comment 3 Alan Stearns 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.
Comment 4 Michelangelo De Simone 2013-06-13 20:25:27 PDT
Still repros on today's nightly (r151543)
Comment 5 Mihai Balan 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.
Comment 6 Alan Stearns 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.