Closed Bug 286809 Opened 15 years ago Closed 9 years ago
Scripts loaded after BASE href change ignore it
The first of two .js files - this one has an absolute reference to it so is sure to get loaded. The content: alert("The first of the two scripts as been loaded");
The second of two .js files - this one will get loaded if the <BASE href=...> change is respected. The content is: alert("The second of the two scripts has been loaded.\n"+ "This one only makes it if the href change of the BASE element is recognized");
Oops, let me try this again. One line changed in the above code. It is now: document.getElementsByTagName('BASE').href = location.href;
Attachment #177939 - Attachment is obsolete: true
CONFIRMED User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050331 Firefox/1.0+
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug was confirmed in comment 5, but comment 6 obliges me to respond, so I am confirming (see comment 3 for how to run the test) that it still exists in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051007 Firefox/1.6a1 [Deer Park Alpha 2, downloaded today] In addition, since I'm here, may as well do some overdue cleanup. Bug 209275 depends on this one and not the other way round: If this one, gets fixed, that does not imply 209275 gets "fixed", but if 209275 is "fixed" that implies this one is fixed. Hence that one depends on this one. I'd also like to reiterate that there is a real use case for developers that I've described in the 2nd half of the original report. Csaba Gabor from Vienna
Please retest now that bug 209275 is fixed?
Today I retested with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:184.108.40.206) It still does not work as expected with FF (ie. 3rd alert is missing) I also tested with IE 8, where it does work as expected (ie. 4 total alerts)
> Today I retested with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; > rv:220.127.116.11) Uh... Is that really what you tested with? That's a build of Firefox _3_. It's not only out of support (and has been for months), but is based on Gecko from back in 2008. So of course it doesn't have this fix, which was checked in in late 2009. To properly test this, you need to test a trunk nightly.
Or the Firefox 4 beta.
WFM. Please reopen if you still see the issue in Firefox 4.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.