Intent to ship: Restrict window.open features parameter

[Tooru Fujisawa]

Summary: `features` parameter of `window.open` [1] has been able to control the visibility of each UI parts separately, only on Firefox and IE. To align with other modern browsers, and to avoid confusing behavior with UI customization and session restore, UI parts related items of `features` parameter are changed to just a condition whether to open a new standard-popup or a new tab.

Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1507375

Standard: This is browser-dependent behavior about the UI. See https://arai-a.github.io/window-open-features/

Platform coverage: All

Preference: None

DevTools bug: None

Target Release: 76

Other browsers: This almost matches to Google Chrome and Safari (except the conditions details). See https://arai-a.github.io/window-open-features/

Tests: covered by mochitest, toolkit/components/windowwatcher/* and browser/base/content/test/popups/browser_popupUI.js and some more

Restricted to secure contexts: No, all non-chrome-priv `window.open` call is changed

Is this feature enabled by default in sandboxed iframes? Yes

[1] https://developer.mozilla.org/en-US/docs/Web/API/Window/open#Window_features <https://developer.mozilla.org/en-US/docs/Web/API/Window/open#Window_features>

--
arai