Closed Bug 81769 Opened 24 years ago Closed 24 years ago

browser urlbar is now updated with the URL of subframes of document

Categories

(SeaMonkey :: Location Bar, defect)

defect
Not set
major

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 82236

People

(Reporter: jrgmorrison, Assigned: radha)

References

Details

(Keywords: regression, Whiteboard: critical for mozilla 0.9.1)

Attachments

(1 file)

As of the evening builds for tonight (Linux 2001051820 and win2k 2001051820), which include jst's fix for bug 60173 "Checking in support for onload handlers for frame and iframe elements, and fixing .ownerDocument of orphan elements, fixes bug 60173, and also fixes part of bug 27382." With these builds, when you visit a frame set page, or a page with inline iframes (read "ad banners"), the urlbar will be updated with the URL of one of the child frames. I'm assuming this is a consequence of jst's fix (which I'm very glad to see!), and that the browser now receives multiple onload events (as the onload events of each child frame now bubble up (jst correct me if that's wrong). Steps to reproduce: 1) go to http://www.aol.com/ or http://www.wired.com/ (type in urlbar and hit enter 2) watch the urlbar as the page loads; the location will be changed more than once during the page load. 3) when the page has loaded, set focus in the urlbar and hit enter (e.g. the page that will be loaded is not the url of the top-level document; it is the url of one of the subframes.
I hereby decorate with magic words (needs a fix for beta).
> I'm assuming this is a consequence of jst's fix (which I'm very glad to see! Er, 'glad to see' that frame load events bubble, which can be useful. Too bad about the side effect.
This messes up history and makes it hard to set proper bookmarks at affected sites. Some might not even realize what's happening and wind up bookmarking some banner frame in good faith. Is severity "major" high enough?
bug 50427 was once critical/P1
Is this caused by bubbling onload events in XUL? If so we can easily (and should) fix that in the XUL code, lemme know, I whip up a fix for that.
*** Bug 81806 has been marked as a duplicate of this bug. ***
(adding blizzard's notation from duplicate bug 81806). jst: I haven't looked through this in detail. I'm not sure what you meant by "caused by bubbling onload events in XUL", but I don't think it is a bad thing to have these events bubble up from _content into the xul window. It's just that the app logic needs to distinguish between the onload of the 'top-level' document, and the onload of subframes in its event listeners (or that's what I think it is).
Whiteboard: critical for mozilla 0.9.1
This is unrelated to my frame/iframe onload event changes (which turned out to not even work at the moment because of some nsIWebProgress fu), I backed out my changes and I'm still seeing this problem.
Oops, sorry for jumping to that conclusion. And, If I had looked a bit closer, I would have seen that the frame loads were already being caught in the browser js anyways. But, I don't know what changed (but it was between 12:00 noon and about 10pm Friday, based on the verification builds that came out.
*** Bug 81858 has been marked as a duplicate of this bug. ***
*** Bug 81921 has been marked as a duplicate of this bug. ***
Component: XP Apps: GUI Features → URL Bar
QA Contact: sairuh → claudius
*** Bug 81992 has been marked as a duplicate of this bug. ***
*** Bug 82070 has been marked as a duplicate of this bug. ***
*** Bug 82115 has been marked as a duplicate of this bug. ***
For window frames, bookmarking appears to work properly, despite the location bar problem. The top (z) frame is bookmarked, not one of the children.
Fix to bug 58906 caused this regression. taking from blake.
Assignee: blakeross → radha
Er, the fix to bug 56062 caused this (that's the one you meant, right?)
*** Bug 82546 has been marked as a duplicate of this bug. ***
Adding self to cc list. I think this is the bug that is goofing up the reloading of my frameset site. Everything gets horked on a reload. Wasn't a problem in .9 David
*** Bug 82675 has been marked as a duplicate of this bug. ***
I'm marking this a dupe of 82236, even though this one came thro' earlier. 82236 describes another side effect that I want to monitor. *** This bug has been marked as a duplicate of 82236 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
*** Bug 82784 has been marked as a duplicate of this bug. ***
Marking verified per comments.
Status: RESOLVED → VERIFIED
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: