1334844 - Address bar uses most recently entered URL, not URL in bar, after using CTRL+ENTER

Status: VERIFIED FIXED

(Firefox :: Address Bar, defect, P2)

Description

[gpuleo]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0
Build ID: 20170125094131

Steps to reproduce:

Step 1: Open a tab. Navigate to any webpage, e.g., cnn.com
Step 2: Open another tab. Navigate to a different webpage, e.g., facebook.com
Step 3: Return to first tab. Hit "enter" in address bar.


Actual results:

Firefox loads the URL that was entered in the second tab (in this example, Facebook), rather than the URL in the address bar of the first tab.


Expected results:

Firefox should load the URL already listed in the address bar of the first tab (in the example, CNN).

Comment 1

[gpuleo]

On reviewing the report-writing guidelines I realize my use of the word "navigate" is imprecise. By "navigate", I mean: type the given URL into the address bar and press Enter.

Comment 2

[marcino245]

Have you run http://kb.mozillazine.org/Standard_diagnostic_-_Firefox ? I had a similiar bug caused by an add-on --> Bug 1248120

Comment 3

[marcino245]

Yet another similiar bug on 51+: Bug 1334748

> Linda

> Another weird thing is that when you open a tab, like troubleshooting info,
> then switch back to the Google tab, the Google tab now shows the
> troubleshooting page.

Comment 4

[Linda]

These bugs are related:

https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1627239
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1659988

In bug 1659988, in the 3rd patch file of /etc/apparmor.d/usr.bin.firefox, if you change the line (70):

   owner /dev/shm/org.chromium.* c,

to

   owner /dev/shm/org.chromium.* rw,

Apply it to /etc/apparmor.d/usr.bin.firefox

Then, sudo apparmor_parser -r /etc/apparmor.d/usr.bin.firefox

it fixes it.

That is, the patch file:

***************************************

36a37,39
>   dbus (send)
>        bus=session
>        interface=org.gtk.vfs.MountTracker,
44a48
>   @{PROC}/[0-9]*/net/arp r,
65c69,70
<   owner /{,var/}run/shm/shmfd-* rw,
---
>   owner /{dev,{,var/}run}/shm/shmfd-* rw,
>   owner /dev/shm/org.chromium.* rw,
206a212
>     /usr/share/distro-info/debian.csv r,
209a216
>     /usr/include/python3.[0-5]/pyconfig.h r,
214c221
<     /usr/local/lib/python3.[0-4]/dist-packages/ r,
---
>     /usr/local/lib/python3.[0-5]/dist-packages/ r,
216c223
<     /usr/bin/python3.[0-4] r,
---
>     /usr/bin/python3.[0-5] r,

***************************************

No clue what most of this does, or if it's all necessary, but the line that made the difference (noted above), and the parts about changing python from 3.4 to 3.5, probably helped.

What a waste of weekend.

I'm looking for a job.  Do you want to hire me?

Comment 5

[Linda]

Sorry, I meant to enter the last post under bug #1334748, but I don't know how to delete it.

Maybe a moderator can delete it?

Comment 6

[Loic]

gpuleo, is it reproducible:

1) in safe mode:
https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode

2) with a fresh profile:
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

Comment 7

[gpuleo]

I can reliably reproduce the bug in safe mode. I was initially able to reproduce the bug on a fresh profile (outside of safe mode), but unable to reproduce it after trying safe mode on a fresh profile, and after switching back to non-safe mode, could not reproduce the bug reliably on the fresh profile.

Comment 8

[Aleksei Vasiliev]

I'm having same bug and can also reproduce in Safe Mode.

Comment 9

[Marco Bonardo [:mak]]

(In reply to gpuleo from comment #0)
> Step 1: Open a tab. Navigate to any webpage, e.g., cnn.com
> Step 2: Open another tab. Navigate to a different webpage, e.g., facebook.com
> Step 3: Return to first tab. Hit "enter" in address bar.

it's missing a step here, how did you select the address bar? Just moving to a different tab doesn't focus it.

Comment 10

[gpuleo]

(In reply to Marco Bonardo [::mak] from comment #9)
> (In reply to gpuleo from comment #0)
> > Step 1: Open a tab. Navigate to any webpage, e.g., cnn.com
> > Step 2: Open another tab. Navigate to a different webpage, e.g., facebook.com
> > Step 3: Return to first tab. Hit "enter" in address bar.
> 
> it's missing a step here, how did you select the address bar? Just moving to
> a different tab doesn't focus it.

I have observed this bug both when clicking in the address bar to select it, and when using Ctrl-L to select the address bar.

Comment 11

[Marco Bonardo [:mak]]

It would be nice to have a way to reproduce this easily, as it is sounds like something really intermittent, and I've never hit it.

Comment 13

[Marco Bonardo [:mak]]

did you use ctrl+enter to visit the first page, by chance?

Comment 14

[Aleksei Vasiliev]

I did, yes. Also happens after Shift+Enter and Ctrl+Shift+Enter for net and org.

Comment 16

[Loic]

Do we have clear STRs?

Comment 17

[Loic]

[Tracking Requested - why for this release]:

[Tracking Requested - why for this release]:

[Tracking Requested - why for this release]:

[Tracking Requested - why for this release]:

STR:
1) Type "example" in the location bar and press Ctrl+Enter
NB: Firefox loads http://www.example.com/
2) Click on the link "More information..."
NB: Firefox loads http://www.iana.org/domains/reserved
3) Select the location bar and press Enter.

Result: Firefox reloads http://www.example.com/ instead of http://www.iana.org/domains/reserved

Regression range:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=f03e2740d604d339ed553dad62a3fc54c317f8fa&tochange=0c899672fff6ae00f5b3affbec48ee4daac35fa1

Comment 18

[Julien Cristau [:jcristau]]

Sounds like a reproducible regression from bug 1306639, tracking for 52/53/54.

Comment 19

[Julien Cristau [:jcristau]]

Too late for 52 now.  Marco, have you had a chance to look at this?

Comment 20

[Marco Bonardo [:mak]]

(In reply to Julien Cristau [:jcristau] from comment #19)
> Too late for 52 now.  Marco, have you had a chance to look at this?

the dependent bug has a patch waiting for review (and it fixes this one as well).

Comment 21

[Marco Bonardo [:mak]]

Fixed by bug 1337682

Comment 22

[Emil Ghitta, QA [:emilghitta]]

I’ve reproduced the issue described in comment 0 by following the steps in comment 17 using an affected build: Firefox 54.0a1(Build Id:20170125030214).

I have verified that the issue is not reproducible using Firefox 53.0b1(Build Id:20170307064827) and Firefox 54.0a2 (Build Id:20170309004016) using Windows 10 64bit and Ubuntu 16.04 16bit.