[Rollout] [Linux] The microsurvey is NOT fully visible if the FxA button is placed in the left most position in the Toolbar and the Window maximized
Categories
(Firefox :: Messaging System, defect, P3)
Tracking
()
People
(Reporter: cmuresan, Unassigned)
References
Details
Attachments
(1 file)
|
723.66 KB,
image/png
|
Details |
[Affected versions]:
- Firefox Release 128.0.3 BuildID 20240725162350
- Firefox Release 130.0.1 BuildID 20240913135723
- Firefox RC 131.0 BuildID 20240923135042
- Firefox Nightly 132.0a1 BuildID 20240925152840
[Affected Platforms]:
- Ubuntu 22.04
[Prerequisites]:
- Have a Firefox Release 128 or up using the en-*, de, or fr locales installed.
- Have a Firefox profile created more than 24 days in the past.
- Have the
browser.search.regionpref set toUS,DE, orFR. - Have the
browser.newtabpage.activity-stream.asrouter.userprefs.cfr.featurespref set totrue. - Have the
nimbus.debugpref set totrue. - Have the
messaging-system.rsexperimentloader.collection_idset tonimbus-preview - Have the Firefox profile signed into sync using an account connected to at least 2 devices.
[Steps to reproduce]:
- Open the browser from prerequisites using a the profile from prerequisites.
- Customize the Browser Toolbar and move the FxA button to the left most position (left of the Back button).
- Confirm the changes and maximize the window.
- Open a new tab and observe the left part of the screen.
[Expected result]:
- The survey is fully visible.
[Actual result]:
- The survey is opened to the left of the window and most of it is not visible.
[Notes]:
- The issue is not reproducible on Windows and macOS. The message is fully displayed, but the anchor point is not visible.
- Attached a screenshot of the issue.
| Reporter | ||
Updated•2 years ago
|
This is an edge case with a customize placement of Fx account avatar. We'll look at the recipe and decide whether to update the message configuration. This may be a lower level issue with the panel component itself. We will investigate.
Comment 2•2 years ago
|
||
Meg -- I know this got marked as a low priority bug. That said, we're thinking of excluding Linux users in the recipe configuration to avoid this scenario. Does this seem like an acceptable solution? Or are there any other suggestions you might have here? This survey will be timeboxed and we'll still be able to get the feedback we're looking for with Android and MacOS users.
Excluding Linux sounds like a reasonable approach.
Description
•