Closed Bug 479212 Opened 16 years ago Closed 16 years ago

Location bar empty when user enters about:blank on existing tab

Categories

(SeaMonkey :: Location Bar, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
seamonkey2.0b1

People

(Reporter: misak.bugzilla, Assigned: misak.bugzilla)

References

Details

(Keywords: regression)

Attachments

(1 file, 2 obsolete files)

After bug 425480 landing, we get same Firefox behavior - Location bar stays empty when user enters about:blank on new tab. But if you enter about:blank on existing tab with already loaded URL, about:blank shows on location bar.
If Firefox people confirms that bug, it can be moved to toolkit.

Reproducible: Allways
I can't reproduce this in Firefox. about:blank only gets put in the location bar if the window has an opener, are you sure that isn't what you're seeing? SeaMonkey also had that behavior since before bug 425480, though, as far as I can tell...
Sorry, slight mix-up here. When the window has an opener, we always show about:blank in the location bar. This is correct and has not changed. However, SeaMonkey also used to show about:blank in a tab if that tab had previous history. However if you open about:blank in an existing tab then the location bar goes blank instead of remaining at about:blank which it used to do.
Summary: Location bar stays empty when user enters about:blank on new tab → Location bar empty when user enters about:blank on existing tab
Attached patch check getWebNavigation().canGoBack too (obsolete) (deleted) — Splinter Review
Ok, old if before bug 425480 brings things back. Also I've included fix for typo in patch from bug 425480 Neil pointed.
Assignee: nobody → misak
Status: NEW → ASSIGNED
Attachment #363133 - Flags: superreview?(neil)
Attachment #363133 - Flags: review?(neil)
Attachment #363133 - Flags: superreview?(neil)
Attachment #363133 - Flags: superreview+
Attachment #363133 - Flags: review?(neil)
Attachment #363133 - Flags: review+
Comment on attachment 363133 [details] [diff] [review]
check getWebNavigation().canGoBack too

>-  if (uri.spec == "about:blank")
>-    value = content.opener ? "about:blank" : "";
>+  if (uri.spec == "about:blank" && !getWebNavigation().canGoBack && !content.opener)
>+    value = "";
Well, this works, but you could have added the check in the ?: line instead.
(In reply to comment #4)
> Well, this works, but you could have added the check in the ?: line instead.
(This refers to an earlier revision of the patch from pastebin which Misak claimed not to work but which worked fine for me...)
Keywords: checkin-needed
Attached patch like this ? (obsolete) (deleted) — Splinter Review
Ok, you confused me on IRC ;) It should be getWebNavigation().canGoBack - braces are required, that's why it doesn't work :)
Attachment #363277 - Flags: superreview?(neil)
Attachment #363277 - Flags: review?(neil)
Attachment #363277 - Flags: superreview?(neil)
Attachment #363277 - Flags: superreview+
Attachment #363277 - Flags: review?(neil)
Attachment #363277 - Flags: review+
Comment on attachment 363277 [details] [diff] [review]
like this ?

>+    value = (content.opener || getWebNavigation().canGoBack) ? "about:blank" : "";
              ^                                              ^
Actually it's these ones you don't need. I forgot there were two sets :-(
Now i got it :)
Attachment #363133 - Attachment is obsolete: true
Attachment #363277 - Attachment is obsolete: true
Comment on attachment 363292 [details] [diff] [review]
for checkin
[Checkin: Comment 9]


http://hg.mozilla.org/comm-central/rev/f99c51271d92
Attachment #363292 - Attachment description: for checkin → for checkin [Checkin: Comment 9]
Blocks: 425480
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: