Closed
Bug 49874
Opened 24 years ago
Closed 23 years ago
iframes and frames require reflow to load their documents
Categories
(Core :: Layout: Images, Video, and HTML Frames, defect, P3)
Core
Layout: Images, Video, and HTML Frames
Tracking
()
RESOLVED
FIXED
mozilla0.9.6
People
(Reporter: brendan, Assigned: hyatt)
References
Details
Attachments
(1 file)
10.36 KB,
patch
|
jag+mozilla
:
review+
|
Details | Diff | Splinter Review |
This has led to bugs with onload firing to early, and is complicating other
modules such as XBL. Asynchronous reflow makes things even more complicated.
It might be good to know *why* only frames require a reflow to load their docs,
and not top-level windows, but hyatt points out that this glaring special case
predates the introduction of asynchronous reflow.
Waterson, we think you are the man to fix this one. Or otherwise to make us all
happy and blissful. Don't make us cry now.
/be
Comment 1•24 years ago
|
||
Talked with brendan & hyatt about this yesterday. When the IFRAME code was
originally written, *all* reflows were done synchronously. Once we added
asynchronous reflow, we violated that assumption.
I think that this could cause ONLOAD problems for documents with IFRAMES,
specifically, the following race:
- IFRAME appears in last content batch, frame is constructed but not flowed.
- Reflow is enqueued, but doesn't fire because reflow timer suppresses it.
- outer URL completes, removes self from load group, active URL count goes to
zero
- outer doc's ONLOAD handler fires
- Reflow timer fires, causing IFRAME to be reflowed, kicking off inner load
There are two ways to fix this:
1. Move IFRAME docshell initialization and URL loading to frame constructor.
(Issues with zero w&h docshell?)
2. Force synchronous reflow when IFRAME is detected.
I believe that (1) would be the more elegant solution, but am not sure if there
are issues? (Images kick of load during frame construction, right?)
Anyway, this is not likely to be a huge issue, so futuring for now.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Assignee | ||
Updated•24 years ago
|
Target Milestone: Future → mozilla0.9.1
Updated•24 years ago
|
Target Milestone: mozilla0.9.1 → mozilla0.9.2
Updated•23 years ago
|
Target Milestone: mozilla0.9.2 → mozilla1.0
Assignee | ||
Comment 3•23 years ago
|
||
Bring it. I'm fixing this NOW. ;)
Assignee: waterson → hyatt
Status: ASSIGNED → NEW
Assignee | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Target Milestone: mozilla1.0 → mozilla0.9.6
Assignee | ||
Comment 4•23 years ago
|
||
Assignee | ||
Comment 5•23 years ago
|
||
Ready for r/sr.
Comment 6•23 years ago
|
||
Comment on attachment 49663 [details] [diff] [review]
Patch to fix this bug as well as 98109
r=jag
Attachment #49663 -
Flags: review+
Assignee | ||
Comment 7•23 years ago
|
||
Fixed.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 8•23 years ago
|
||
*** Bug 100502 has been marked as a duplicate of this bug. ***
Updated•6 years ago
|
Product: Core → Core Graveyard
Updated•6 years ago
|
Component: Layout: HTML Frames → Layout: Images
Product: Core Graveyard → Core
You need to log in
before you can comment on or make changes to this bug.
Description
•