User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0) Gecko/20100101 Firefox/7.0 Build ID: 20110816154714 Steps to reproduce: Trigger a XUL Errorpage by going to a nonexisting or invalid url like http://www.nonexistingurl.com/ http://127.0.0.1:213 Then copy the url to the clipboard using either ctrl+c or the context menu. Actual results: The url is copied to the clipboard without the http:// (like displayed in location bar) Expected results: http:// should have been prepended to the url the same way it is prepended when visiting working urls.
confirmed on http://hg.mozilla.org/mozilla-central/rev/f41df039db03 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0a1) Gecko/20110822 Firefox/9.0a1 ID:20110822030805 Regression window: Works: http://hg.mozilla.org/mozilla-central/rev/48e72227c2fa Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0a1) Gecko/20110623 Firefox/7.0a1 ID:20110623030811 Fails: http://hg.mozilla.org/mozilla-central/rev/5028de4c95e9 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0a1) Gecko/20110623 Firefox/7.0a1 ID:20110623013442 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=48e72227c2fa
Status: UNCONFIRMED → NEW
Ever confirmed: true
Sorry, Paste error Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=48e72227c2fa&tochange=5028de4c95e9
> Trigger a XUL Errorpage by going to a nonexisting or invalid url like > http://www.nonexistingurl.com/ Interestingly, this works for me when I follow your link here, but fails when I open it in a new tab.
(In reply to Dão Gottwald [:dao] from comment #3) > Interestingly, this works for me when I follow your link here, but fails > when I open it in a new tab. Presumably this is because the URL is considered "typed" in the latter case, due to the background error page load not triggering an onLocationChange to override the set of userTypedValue for the new tab? Reminds me of bug 623155.
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Last Resolved: 9 months ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.