-
Notifications
You must be signed in to change notification settings - Fork 113
resource://activity-stream/data/content/activity-stream.bundle.js changes restored new tab title to "undefined" when switching to another tab #2819
Comments
A similar thing should be running Firefox with "about:newtab" as a command line argument to have it open about:newtab as early as possible. I can reproduce this on Linux (not OS X). |
Actually, maybe I can't quite reproduce the same issue. I think I'm running into a separate issue where the page's |
I am running Linux Mint and my current build is Mozilla/5.0 (X11; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0 ID:20170705170343 CSet: 11755fd63168581e194258d04bb6a7337779ec78 First I was looking in the console tab in DevTools, but actually there are these errors in the browser console right after Nightly starts up:
(It's a localized build, so |
Okay, so I might be running into the same thing locally then. Just to confirm, the new tab page is almost empty except for the fox icon in the top left and the banner at the bottom of the page? And just to double check, when you get into the state of "undefined" as the title, if you check |
Well, maybe it's a slightly different behavior what we see after all. So I was playing around a bit and the problem only occurs when I have
When I change the Firefox homepage to something different from about:newtab, I cannot reproduce anymore. That's interesting, because Firefox should not care about the homepage preference and just load tabs from the last session. It seems to me, that Firefox displays the homepage according to the preferences first and than replaces it by the actual tab content. And for some reason, it fails, when those two are the same ( |
We can stop the new tab title changing to "undefined" on tab-away by only adding the This unfortunately does not solve the issue of the page content not rendering. |
I think this might be caused by the In my testing, when Firefox starts without the issue, then |
Sounds like we can avoid this issue by starting up earlier so that RemotePages can initialize before any about:newtab tabs are loaded. One way to do that is reverting 86547df but would then reintroduce talos sessionstore regressions. Also would be useful to note that moving startup earlier will probably break the test making sure various services/modules aren't loaded until later. More complex would be to somehow register RemotePages early on while deferring the rest of ActivityStream.jsm and related loads. @k88hudson any ideas on how this can be done quickly and maybe not-so-complexly? |
Oh, and Mossop just suggested having AboutNewTab just pass RemotePages instance off to ActivityStream... that's kinda neat. |
Also see https://bugzilla.mozilla.org/show_bug.cgi?id=1382139
I was unable to reproduce this with mozregression nor clean profile, but this still happens even after I have disabled all add-ons, so it's likely to happen for users with used profile when Activity Stream is in Firefox.
STR (see this video):
The cause is a call from Base.componentDidMount() on visibilitychange event to updateTitle() with _ref3 variable in uninitialized state. Personally I am not sure why this happens or in which cases should be the tab title changed at all. But the fix should be easy, check the _ref3 state or the string existence before it is actually used for document.title.
The text was updated successfully, but these errors were encountered: