### Beta/Release Uplift Approval Request * **User impact if declined**: Users browsing one of the quarantined domains with extensions not monitored by Mozilla. This isn't a lot of users but it might be confusing for users to notice an add-on not working and nothing else. While there is a notification in the extensions panel, there is no UI hint to tell the user to open that panel. With these 2 patches, users should see the "notification dot" under an extension or the extensions button. * **Is this code covered by automated tests?**: Yes * **Has the fix been verified in Nightly?**: No * **Needs manual test from QE?**: No * **If yes, steps to reproduce**: * **List of other uplifts needed**: None * **Risk to taking this patch**: Low * **Why is the change risky/not risky? (and alternatives if risky)**: This is a small 2-patch stack that has automated test coverage. * **String changes made/needed**: * **Is Android affected?**: No
Bug 1836448 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
### Beta/Release Uplift Approval Request * **User impact if declined**: Users browsing one of the quarantined domains with extensions not monitored by Mozilla. This isn't a lot of users but it might be confusing for users to notice an add-on not working and nothing else. While there is a notification in the extensions panel, there is no UI hint to tell the user to open that panel. With these 2 patches, users should see the "notification dot" under an extension or the extensions button. * **Is this code covered by automated tests?**: Yes * **Has the fix been verified in Nightly?**: No * **Needs manual test from QE?**: No * **If yes, steps to reproduce**: * **List of other uplifts needed**: None * **Risk to taking this patch**: Low * **Why is the change risky/not risky? (and alternatives if risky)**: This is a small 2-patch stack that has automated test coverage. * **String changes made/needed**: Yes * **Is Android affected?**: No