- removes `about:firefoxview-next` route
- `about:firefoxview` now points to `firefoxview-next.html` (until we rename)
- remove pref for `browser.tabs.firefox-view-next`
- preserve pref for `browser.tabs.firefox-view-newIcon` as part of firefoxViewNext feature manifest (until experiment is over)
- whitelist unreferenced files in `browser_all_files_referenced.js` as they will be removed in child Bug 1869833
Differential Revision: https://phabricator.services.mozilla.com/D196093
- removes `about:firefoxview-next` route
- `about:firefoxview` now points to `firefoxview-next.html` (until we rename)
- remove pref for `browser.tabs.firefox-view-next`
- preserve pref for `browser.tabs.firefox-view-newIcon` as part of firefoxViewNext feature manifest (until experiment is over)
- whitelist unreferenced files in `browser_all_files_referenced.js` as they will be removed in child Bug 1869833
Differential Revision: https://phabricator.services.mozilla.com/D196093
Notification can be triggered locally via this snippet:
```js
BrowserSearch.removalOfSearchEngineNotificationBox("Google", "Foogle")
```
Differential Revision: https://phabricator.services.mozilla.com/D194312
This patch updates the `NotificationMessage` element in `notificationbox.js` so that it extends our newer `moz-message-bar` component instead of the deprecated `message-bar` component. Many of the changes are just dealing with the implications of making things async (so that we can ensure `moz-message-bar.mjs` gets imported). I tried to break out places where I modified related code and tests into separate patches to mitigate some of the review pain here.
This patch solves a longstanding issue where we were loading `in-content/common-shared.css` in the chrome since it gets used by the `message-bar` element. It also makes some small visual changes to our infobars (slight outline, icon colors, adds a bit of spacing).
Differential Revision: https://phabricator.services.mozilla.com/D189872
- removes `about:firefoxview-next` route
- `about:firefoxview` now points to `firefoxview-next.html` (until we rename)
- remove pref for `browser.tabs.firefox-view-next`
- preserve pref for `browser.tabs.firefox-view-newIcon` as part of firefoxViewNext feature manifest (until experiment is over)
- whitelist unreferenced files in `browser_all_files_referenced.js` as they will be removed in child Bug 1869833
Differential Revision: https://phabricator.services.mozilla.com/D196093
- removes about:firefoxview-next route
- about:firefoxview now points to firefoxview-next.html (until we rename)
- remove pref for browser.tabs.firefox-view-next
- preserve pref for browser.tabs.firefox-view-newIcon as part of firefoxViewNext feature manifest (until experiment is over)
Depends on D196080
Differential Revision: https://phabricator.services.mozilla.com/D196093
Connects content analysis checks with the tab that their messages
to the user should appear on. Adds notifications for the
CA messages.
Differential Revision: https://phabricator.services.mozilla.com/D191784
When using the accent color in the titlebar we apply InactiveCaption
color, but then we also apply this opacity which causes the text to be
super dark.
Use color-mix() rather than opacity on the lwtheme case, so that it
works on Linux and macOS when themes are used too.
Adapt browser-custom-colors.css to do this for the system theme on
Windows and macOS so that there's no behavior change.
For high contrast and Linux, InactiveCaption should have us covered.
Depends on D190952
Differential Revision: https://phabricator.services.mozilla.com/D190953
This is just Olli's patch unedited. Still in the process of double
checking on try, but it appears that this doesn't break any tests
and seems to work just fine. This patch just avoids showing the
status bar and updating the stop/reload button when loading iframe
content. This should not affect top level loads, and this matches
Chrome's behavior.
Differential Revision: https://phabricator.services.mozilla.com/D190616
This is just Olli's patch unedited. Still in the process of double
checking on try, but it appears that this doesn't break any tests
and seems to work just fine. This patch just avoids showing the
status bar and updating the stop/reload button when loading iframe
content. This should not affect top level loads, and this matches
Chrome's behavior.
Differential Revision: https://phabricator.services.mozilla.com/D190616
