Closed Bug 135188 Opened 23 years ago Closed 23 years ago

about:blank should not appear in Location Bar when switching between new tabs

Categories

(SeaMonkey :: Location Bar, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 104778

People

(Reporter: deleted48206, Assigned: hewitt)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020312 BuildID: All since 0.9.9 Everytime I open a new tab I get just a blank URL-Location bar but when I open several tabs and then switch from one to another all the newly focused tabs show the message "about:blank" in the location bar. This is first of no use, second not informative (for what?), and third very disturbing when trying to quick copy/paste an address the way X does: You mark something, switch back to mozilla, want to paste it into the location field by clicking third mouse button but there is already "about:blank" in the location bar. You may paste your address behind "about:blank" and then delete "about:blank" (very ugly solution) or you mark "about:blank" to delete it first and loose the address to be pasted because X now remembers the last marked "about:blank". There are other disturbing points but I think this is enough to understand why this message is just boring and driving users into madness. Reproducible: Always Steps to Reproduce: 1.open several new tabs 2.switch between the new tabs 3.look at the URL bar Actual Results: You see "about:blank" in the URL bar Expected Results: You see a blank URL bar This drives me mad!
Confirming on Win2K, 2002040303. Marking as new.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: please drop about:blank messages!!!!!! → about:blank should not appear in Location Bar when switching between new tabs
bug 104778 bug 103720 bug 111874 *** This bug has been marked as a duplicate of 104778 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
VERIFIED DUPLICATE
Status: RESOLVED → VERIFIED
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.