We currently show a full URL as the initial tab title (e.g. "https://www.mozilla.org/en-US/") until the page loads and we know the actual page title. When loading multiple tabs, such as during session restore, many tabs will have the same undifferentiated tab title prefix like "https://www....". Since the URL scheme and "www." subdomain are not meaningful to users, just show the URL's hostname without any "www." prefix (e.g. "mozilla.org").
Other browsers' initial tab titles for comparison:
* Firefox 54 uses "Connecting...".
* IE11 uses the same "hostname without www" placeholder as this changeset.
* Edge uses "Blank page".
* Chrome uses "Loading..." on Windows and "Untitled" on Mac.
* Safari uses "Untitled".
MozReview-Commit-ID: JxLxvBjpIBh
This test case documents the current behavior of about: pages's initial tab titles. The fix for bug 1364127 caused about: pages' initial tab titles to show their about: URIs until their actual page titles are known, e.g. "about:addons" -> "Add-ons Manager". This is bug 1371896. Previously, about: pages' initial tab titles were blank until the page title was known.
This test case uses the about:robots page because its title is not localized, which makes testing easier.
MozReview-Commit-ID: JGaRciaZUEC
DevTools are moving out of mozilla-central and m-c code should only rely on the
DevToolsShim that will remain available in m-c after the migration.
This changeset updates SessionStore.jsm to call the DevToolsShim instead of the
scratchpadmanager.
The actual underlying implementation is the same when devtools are installed and
no-ops when they are not.
MozReview-Commit-ID: Fv22TtjJiDw
The browser-chrome test suite now detects and reports unhandled rejections of native Promises, in addition to those created by Promise.jsm. The whitelisting mechanism is updated to use primarily the PromiseTestUtils.expectUncaughtRejection function. Tests will fail if a rejection that is not whitelisted occurs, or if a whitelisted rejection does not occur anymore.
MozReview-Commit-ID: 1beGB5GG8Ty
The browser-chrome test suite now detects and reports unhandled rejections of native Promises, in addition to those created by Promise.jsm. The whitelisting mechanism is updated to use primarily the PromiseTestUtils.expectUncaughtRejection function. Tests will fail if a rejection that is not whitelisted occurs, or if a whitelisted rejection does not occur anymore.
MozReview-Commit-ID: 1beGB5GG8Ty
DevTools are moving out of mozilla central, and since this test is relying on scratchpad
being available, it would probably make sense to move it to the scratchpad test suite
which will still be run in the new devtools continuous integration setup.
MozReview-Commit-ID: 19x6Ccp85ND
This change means that any related http pages driven through content (window.open, links, etc.) will continue to be loaded in the file content process.
Same-origin loads via the UI will also remain in the file content process.
Cross-origin loads via the UI will cause a process switch.
History navigation will stay in the process, if it was originally loaded in that process.
If the tab was resumed before, it could start playing any autoplay media without user's
permission after session restore.
MozReview-Commit-ID: C3DHIIsLtJA
Robot favicon (image/png) is currently only used in about:robots
(browser/base/content/aboutRobots.xhtml), but we intend to re-use this
resource for indicating that the browser is under remote (robot) control.
MozReview-Commit-ID: 4eTNbAITPQx
While setTab does end up setting the label and icon, it also does completely different and more crucial things. This call really doesn't belong in updateTabLabelAndIcon.
MozReview-Commit-ID: 1ZSY17ThNx
While setTab does end up setting the label and icon, it also does completely different and more crucial things. This call really doesn't belong in updateTabLabelAndIcon.
MozReview-Commit-ID: 9HXYS0fXgRN
