Summary: | Should media query callbacks be fired asynchronously? | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | zalan <zalan> | ||||
Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | NEW --- | ||||||
Severity: | Normal | CC: | ap, bfulgham, dino, rniwa, simon.fraser, webkit-bug-importer, zalan | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | WebKit Nightly Build | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Created attachment 312809 [details] Test case Currently Document::evaluateMediaQueryList() fires then synchronously through FrameView::layout. Since the callback could run any JS code, we might not be able to recover from it when climbing back on the callstack with nested frames. See attached testcase (run-webkit-test --debug -1)