Closed Bug 293627 Opened 19 years ago Closed 19 years ago

Unconventional URL compromises tab navigation

Categories

(Firefox :: Tabbed Browser, defect)

x86
Linux
defect
Not set
major

Tracking

()

RESOLVED INVALID

People

(Reporter: softexpert, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050508 Firefox/1.0+
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050508 Firefox/1.0+

When you try to navigate to a "special" url - that is one that has , and {}
characters in it - the active tab becomes unfunctional: it grays out and you
cannot close it.
On my actual build (Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2)
Gecko/20050508 Firefox/1.0+) I don't see any javascript errors or exceptions.

Reproducible: Always

Steps to Reproduce:
1. Open a new tab.
2. Copy and paste the above link.
3. Try to navigate ... well you can't !!

Actual Results:  
The active tab becomes unfunctional: it grays out and you cannot close it.

Expected Results:  
The link should display normally
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050509
Firefox/1.0+

Works for me on windows.
WFM, Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050509 Firefox/1.0+
(In reply to comment #2)
> WFM, Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050509 Firefox/1.0+

OK, I got it: it occurs only when AdBlock extension is enabled.
As a "bonus", when the bug has occured, I cannot close the window from the
File/Quit option, I have to click on the right upper corner.

In my opinion, there are some exploitable flaws in there and they are just a
little highlighted by this bug.
(In reply to comment #3)
> OK, I got it: it occurs only when AdBlock extension is enabled.

Please report the bug to the AdBlock developers.

->INVALID

p.s. If you can demonstrate the "exploitable flaws" with extensions disabled
then please reopen the bug.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.