Bug 36334
| Summary: | pageshow event should be dispatched asynchronously | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Brady Eidson <beidson> |
| Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | ap, fishd, louisedazzle15 |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Brady Eidson
pageshow event should be dispatched asynchronously
see step #4.5 of the history traversal algorithm (section 6.5.9):
http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html#traverse-the-history
this is (probably) a recent change to the spec
Found when exploring fixing https://bugs.webkit.org/show_bug.cgi?id=36201 and https://bugs.webkit.org/show_bug.cgi?id=36202
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Brady Eidson
<rdar://problem/7769669>
Alexey Proskuryakov
Would there be an observable difference?
Darin Fisher (:fishd, Google)
You could probably observe this on an iframe in the same origin.