Alert "Is not a registered protocol" when view source after javascript location change



16 years ago
9 years ago


(Reporter: teilo+bugzilla, Unassigned)


Windows XP

Firefox Tracking Flags

(Not tracked)




(1 attachment)



16 years ago
The alert "Is not a registered protocol" is shown when viewing source after
using a *specific* piece of javascript after viewing the about:credits page

Steps to reproduce,

1)Start Mozilla
2)goto about:credits
3) paste the following into the location bar (should go to parent web page)
javascript:var urlStr = new String(location.href);
while(urlStr.charAt(urlStr.length-1) == '/') urlStr = urlStr.substring(0,
urlStr.length-2); var lastInd = urlStr.lastIndexOf('/');  var newUrl =
urlStr.substring(0, lastInd + 1);location.href = newUrl;
4) Choose view source from the menu

Actual Results
1) Location bar changes URL to
2) On view source the Alter "Is not a valid protocol" is displayed

Expected results,
1) The javascript fails because the location in about:credits
1) the view source shows the source of the page

Comment 1

16 years ago
Created attachment 118540 [details]
error message

I get this message constantly (sometimes 100% of the time) when I click on a
link.  After I accept the error by clicking "OK", then the browser accesses the
link properly.	I cannot see any special pattern to this.  See also Bugs: 
176822,  183773, 194717, 199261
Product: Browser → Seamonkey
Assignee: doronr → mrbkap
QA Contact: pmac → doronr

Comment 2

10 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Assignee: mrbkap → nobody
QA Contact: doronr → view-source

Comment 3

9 years ago
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Last Resolved: 9 years ago
Resolution: --- → EXPIRED


9 years ago
Component: View Source → View Source
Product: SeaMonkey → Core Graveyard
You need to log in before you can comment on or make changes to this bug.