Sayed [:LiquidO2] Reporter
	Description • 8 years ago

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20161010030204

Steps to reproduce:

1. Login to facebook.com
2. Edit the text in URL bar (e.g: edit "https://www.facebook.com" to "test" )
3. Now navigate to other page by clicking any button on the page. (Don't navigate by typing URL in the address bar)

Check attached video for clarification


Actual results:

The text in the URL bar remained "test"


Expected results:

The text in the URL bar should be changed to the URL of the new page.

	Marco Bonardo [:mak]
	Comment 2 • 8 years ago

I cannot reproduce this... could you please try in Safe Mode, so we can exclude Add-ons.

	Marco Bonardo [:mak]
	Comment 3 • 8 years ago

https://support.mozilla.org/kb/troubleshoot-firefox-issues-using-safe-mode

	Sayed [:LiquidO2] Reporter
	Comment 4 • 8 years ago

(In reply to Marco Bonardo [::mak] from comment #2)
> I cannot reproduce this... could you please try in Safe Mode, so we can
> exclude Add-ons.

I have tried this in both Linux(64 bit) and Windows 10(64 bit). In both safe mode and fresh profile. Still reproducible. 

BUILD ID   : 20161017030209
USER AGENT : Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

BUILD ID   : 20161017030209
User Agent : Mozilla/5.0 (Windows NT 10.0; rv:52.0) Gecko/20100101 Firefox/52.0

	Marco Bonardo [:mak]
	Comment 5 • 8 years ago

now I can reproduce, it doesn't happen every time, looks like there may be a race condition somewhere.

	arni2033
	Comment 6 • 8 years ago

STR_2:  (assuming comment 0 is STR_1)
1. Open http://example.org/
2. Select all text in urlbar, type "asdf"
3. Open web console, execute  "onclick=()=>{history.pushState("123","123","123");}"  w/o outer quotes
4. Click on the page

AR:  Urlbar displays "asdf"
ER:  Either X or Y
 X) Value should change to "http://example.org/123", because user-generated event handler changed it
 Y) Value should change to "http://example.org/123", because urlbar wasn't focused


This is bug 435932, which was re-introduced by bug 1199934. See bug 1199934 comment 14
(why are you, the component owner, not listed in CC-list in both of those bugs?...)
According to comment 5, bug 435932 deserves "Priority -> P2". I can't set priority, so setting [NI?]

I also checked some builds proving that the issue re-appeared after bug 1199934:
First bad:  mozilla-central   ae7413abfa4d3954a6a4ce7c1613a7100f367f9a  (2016-04-19)
First bad:  mozilla-inbound   67cd0f4372e924d0d9e7bc8c56fc41015191b09e
> http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=f5f9a967&tochange=67cd0f43
Last good:  mozilla-inbound   f5f9a967030d8104686224579294d5aeafff8b5a
Last good:  mozilla-central   1f16d3da9280e40ada252acf8110b91ee1edbb08  (2016-04-18)

	Marco Bonardo [:mak]
	Comment 7 • 8 years ago

(In reply to arni2033 from comment #6)
> (why are you, the component owner, not listed in CC-list in both of those
> bugs?...)

it's hard to remember every single bug when you have thousands to remember. I watch the components though so I don't need to be cc-ed.
I'll move the info there.