STR: 1. Run today's nightly. (I'm running the 64-bit Linux version on Debian testing.) 2. Open a new tab. 3. Type "www.google.com" and press <enter>. Actual results: After you press <enter>, the address bar shows "about:newtab" for a second or so until the page loads, at which point it's replaced by the loaded page address ("https://www.google.ca/"). Expected results: The address bar continues displaying what I typed ("www.google.com") until the page loads. This was the behaviour until recently.

Hey Drew - do you know if there are plans to make about:newtab run in the content process? I couldn't find any open bugs for it, but I might have missed it.

Yes, bug 1021654 and the other bugs in its bug tree, but I don't think it's a high priority right now.

Is this really tied to about:newtab? I have my new tab page set to about:blank and I see the same thing with that. I know it's not a functionality bug, but it is pretty annoying.

I have the same problem with e10s enabled on Windows 8.1 x64. Build 37.0a1 (2014-12-02) and older ones too.

I see the same behaviour as comment 0 (on Linux). It's annoying.

OS X as well.

It makes you think you didn't type it in correctly, and you often have time to focus on the address bar and start typing it in again, and then the page loads and you're left embarrassed and annoyed and hoping nobody saw you :)

Still happening for me. Nightly 39.0a1 with e10s enabled. Annoying bug.

Sometimes this is not brief (I suspect my DNS fails sometimes?) and actually prevents copying/modifying the URL. For example: 1) Type www.ebay.com and hit enter 2) www.ebay.com is replaced with about:newtab while the Connecting... spinner starts 3) I can no longer see that I was trying to go to ebay and I can't copy the URL or modify it This is worst when it's a complex URL that I painstakingly typed from somewhere hit enter and then lose it (in the case of the page never loading). Anyway, mostly wanted to CC myself on this bug. :)

Wil, I think bug 1056443 should have fixed this. It landed on 04-15 and you commented on 04-28. Did you actually observe it on 04-28, or were you just talking about previous observations? Also, can you still reproduce the problem? If so, can you give an STR?

> I think bug 1056443 should have fixed this. It used to be really easy to reproduce for me, but not any more. AFAICT it's fixed. Hooray!

\o/ I won't clear the needinfo on wclouser in case he still sees it. I'll mark it WFM until we hear further though.

After a quick test this also appears fixed to me. I'll see if my DNS acts up again, but so far so good. Thanks. :)

I briefly see about:newtab when closing a tab. Might be completely unrelated. I don't think DNS is involved, just the content goes away before the chrome does.