**Note** * When the user triggers the "Captive portal" info bar and then the "Protocol handler" info bar, he will notice that their display order is incorrect. **Affected versions** * Nightly v90.0a1 * Beta v89.0b7 * Beta v89.0b4 (UNNAFECTED) **Affected platforms** * all **Steps to reproduce** 1. Lunch browser. 2. Load about:config and make: devtools.chrome.enabled = true 3. Open the "Browser console" (ctrl+shift+J / cmd+shift+J) and input: CaptivePortalWatcher._showNotification() Observe: browser-specific notification is displayed across all opened tabs. 4. Load https://www.lookout.net/test/handler/ 5. Change the URL from http to https inside the second input box next to the "Run ad hoc test" button 6. Click the "Run ad hoc test" button **Expected result** * The tab-specific "Protocol handler" infobar is displayed below the browser-specific "Captive portal" infobar. **Actual result** * The tab-specific "Protocol handler" infobar is displayed ABOVE the browser-specific "Captive portal" infobar, incorrectly. **Regression range** * 2021-05-04T15:39:32.175000: DEBUG : Found commit message: Bug 1682676 - Part 3: Test infobars inside of the chrome r=ewright Depends on D104741 Differential Revision: https://phabricator.services.mozilla.com/D106013 **Additional notes** * Issue logged based on the following information from Figma document: "All browser-specific notifications will go in one notificationbox (rather than in gHighPriorityNotificationBox and gNotificationBox). This notificationbox will be above the tab-specific notificationbox, and new notifications are added at the top of the notificationbox. All tab-specific notifications will be shown, with the newest notification at the bottom of the notificationbox."
Bug 1709420 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
**Note** * When the user triggers the "Captive portal" info bar and then the "Protocol handler" info bar, he will notice that their display order is incorrect. **Affected versions** * Nightly v90.0a1 * Beta v89.0b7 * Beta v89.0b4 (UNNAFECTED) **Affected platforms** * all **Steps to reproduce** 1. Launch browser. 2. Load about:config and make: devtools.chrome.enabled = true 3. Open the "Browser console" (ctrl+shift+J / cmd+shift+J) and input: CaptivePortalWatcher._showNotification() Observe: browser-specific notification is displayed across all opened tabs. 4. Load https://www.lookout.net/test/handler/ 5. Change the URL from http to https inside the second input box next to the "Run ad hoc test" button 6. Click the "Run ad hoc test" button **Expected result** * The tab-specific "Protocol handler" infobar is displayed below the browser-specific "Captive portal" infobar. **Actual result** * The tab-specific "Protocol handler" infobar is displayed ABOVE the browser-specific "Captive portal" infobar, incorrectly. **Regression range** * 2021-05-04T15:39:32.175000: DEBUG : Found commit message: Bug 1682676 - Part 3: Test infobars inside of the chrome r=ewright Depends on D104741 Differential Revision: https://phabricator.services.mozilla.com/D106013 **Additional notes** * Issue logged based on the following information from Figma document: "All browser-specific notifications will go in one notificationbox (rather than in gHighPriorityNotificationBox and gNotificationBox). This notificationbox will be above the tab-specific notificationbox, and new notifications are added at the top of the notificationbox. All tab-specific notifications will be shown, with the newest notification at the bottom of the notificationbox."