Closed
Bug 315369
Opened 19 years ago
Closed 18 years ago
frameset does not display when top.window.outerWidth or top.window.outerHeight called before drawing
Categories
(Core :: DOM: HTML Parser, defect, P1)
Core
DOM: HTML Parser
Tracking
()
RESOLVED
FIXED
mozilla1.9alpha1
People
(Reporter: klassej, Assigned: bzbarsky)
References
()
Details
Attachments
(2 files)
229 bytes,
text/html
|
Details | |
1.61 KB,
patch
|
sicking
:
review+
sicking
:
superreview+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20051104 Camino/1.0+ Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20051104 Camino/1.0+ The page renders fine in Safari etc. but doesn't show in Camino. Reproducible: Always Steps to Reproduce: 1. Open http://www.svenskadator.se/ in Camino. 2. 3.
Confirming. Sam or Pink can you tell me if this should be bounced to the Core?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 4•19 years ago
|
||
Possibly a trunk regression of bug 312942, bug 307821, or bug 309712 (all three of which were Core bugs, btw). cl
Comment 6•19 years ago
|
||
It looks like the <script> is screwing it up.
Comment 7•19 years ago
|
||
Maybe not; hmm.
Comment 8•19 years ago
|
||
Nope, that's definitely it. Removing the <script> tag makes the page load.
Comment 9•19 years ago
|
||
Calling top.window.outerWidth or top.window.outerHeight before the page has started drawing causes the page to not render when there's a frameset! Reduced testcase forthcoming.
Comment 10•19 years ago
|
||
Calling top.window.outerWidth or top.window.outerHeight before the page has started drawing causes the page to not render when there's a frameset! Reduced testcase forthcoming.
Comment 11•19 years ago
|
||
Comment 12•19 years ago
|
||
This does *not* occur in the latest Firefox trunk build, so it's definitely Camino-only. (Sorry about the double post above; the radio buttons are a bit too close to the "Commit" button.)
Reporter | ||
Comment 13•19 years ago
|
||
(In reply to comment #12) > This does *not* occur in the latest Firefox trunk build, so it's definitely > Camino-only. > > (Sorry about the double post above; the radio buttons are a bit too close to > the "Commit" button.) > Updated to: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051108 Camino/1.0b1 It now works fine, the content of the page shows.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 14•19 years ago
|
||
This still occurs. It's trunk only; 1.0b1 is on a branch. Reopening.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
This needs a regression window (it's still broken on the trunk)--and then we can bug layout folks ;)
Keywords: qawanted
Summary: The page does not show. → frameset does not display when top.window.outerWidth or top.window.outerHeight called before drawing
Comment 16•18 years ago
|
||
This broke between the 2005-08-24 nightly and the 2005-08-25 nightly.
Keywords: qawanted
(In reply to comment #16) > This broke between the 2005-08-24 nightly and the 2005-08-25 nightly. Checkins in that window: http://tinyurl.com/g9oel The most promising-looking checkin in that group (to me) was one of the split-window bugs, but it was fixed on the trunk and 1.8 (pre-1.8.0), so that can't be it. Boris, do you have any idea which one might have caused this (Camino-Trunk-only) bug?
Assignee | ||
Comment 18•18 years ago
|
||
The checkin for bug 253951 could have done it. Note that that caused regressions which were fixed -- bug 306660, bug 312097, bug 321751. Those are similar in concept to the problem you're describing here... Are you seeing any of those three bugs in Camino, by any chance?
(In reply to comment #18) > The checkin for bug 253951 could have done it. Note that that caused > regressions which were fixed -- bug 306660, bug 312097, bug 321751. Those are > similar in concept to the problem you're describing here... Bug 306660 (URL): works, 1.8.0 and trunk Bug 312097 (URL): works, 1.8.0; broken trunk Bug 321751, attachment 207017 [details]: broken 1.8.0 (as expected*), works trunk. (* the whole body is repainted brown on returning to the page after switching tabs) Bug 321751, attachment 208051 [details]: broken, 1.8.0 (as expected, when loaded in about:blank), works on trunk I put the full table above to help me keep track of what I was seeing, so it's a lot of maybe-useless information ;) I think the only useful bit of info in the "chart" is that bug 312097 is still broken on the trunk in Camino, which would make it the closest cousin to this bug on that basis.
Status: REOPENED → NEW
QA Contact: page.layout
Oops, I meant to put 1.8.1 results, too, before I posted; they're identical to the 1.8.0 results on every case (as, I think, is expected in all those cases).
Assignee | ||
Comment 21•18 years ago
|
||
Ah, bug 312097 is broken on trunk in Firefox too, and I've managed to reproduce this bug in TestGtkEmbed. So we're in business. I see what happened here... It's a regression from bug 311785, more or less.
Assignee: mikepinkerton → mrbkap
Component: Page Layout → HTML: Parser
OS: MacOS X → All
Product: Camino → Core
QA Contact: page.layout → parser
Hardware: Macintosh → All
Assignee | ||
Comment 22•18 years ago
|
||
Assignee: mrbkap → bzbarsky
Status: NEW → ASSIGNED
Attachment #217038 -
Flags: superreview?(bugmail)
Attachment #217038 -
Flags: review?(bugmail)
Assignee | ||
Comment 23•18 years ago
|
||
I'd appreciate a test of that patch in Camino too, of course.
Priority: -- → P1
Target Milestone: --- → mozilla1.9alpha
(In reply to comment #23) > I'd appreciate a test of that patch in Camino too, of course. I just rebuilt Camino with your patch, and it does indeed fix both the testcase here and the one in bug 312097. Thanks Boris!
Comment on attachment 217038 [details] [diff] [review] This seems to fix it... So the bug is in how we grab mFrameset? (in any case this seems like a resonable thing to do since mFrameset doesn't need to be set twice)
Attachment #217038 -
Flags: superreview?(bugmail)
Attachment #217038 -
Flags: superreview+
Attachment #217038 -
Flags: review?(bugmail)
Attachment #217038 -
Flags: review+
Assignee | ||
Comment 26•18 years ago
|
||
Yeah, the bug is that now we're setting mFrameset before the place where we're checking it (without this patch). We need to check it first.
Doh! Of course, i'm with you now.
Assignee | ||
Comment 28•18 years ago
|
||
Fixed.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago → 18 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•