Closed
Bug 1931579
Opened 1 year ago
Closed 1 year ago
Compose Previews are broken and unable to render
Categories
(Firefox for Android :: Design System and Theming, defect, P2)
Tracking
()
RESOLVED
FIXED
134 Branch
| Tracking | Status | |
|---|---|---|
| firefox132 | --- | unaffected |
| firefox133 | --- | unaffected |
| firefox134 | --- | fixed |
People
(Reporter: 007, Assigned: harrisono)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [fxdroid][group3][toolbar-redesign-beta-blocker])
Attachments
(1 obsolete file)
A recent change from a navbar patch nuked Compose previews and all of them are unable to render. Calling components (which is what context.settings() does under the hood), breaks previews, so these calls should be avoided whenever possible.
We would need to either:
- Wrap the settings calls with the
inComposePreviewcheck - “Revert” the change and remove the
isCustomTabcheck fromTheme.getTheme()and instead have a local when check inside of ExternalAppBrowserFragment to directly specify the theme to theFirefoxThemewrapper call.- So we’d have a when to check for the custom tab logic and then just use the default
Theme.getThemeotherwise
- So we’d have a when to check for the custom tab logic and then just use the default
Personally, I’d advocate for option 2. The firefox theme wrapper should probably not have knowledge about custom tabs logic, especially if it’s only used in one location, but also to keep Theme.getTheme as minimal as possible.
| Assignee | ||
Updated•1 year ago
|
Assignee: nobody → hoglesby
Status: NEW → ASSIGNED
Comment 1•1 year ago
|
||
Set release status flags based on info from the regressing bug 1925679
status-firefox132:
--- → unaffected
status-firefox133:
--- → unaffected
status-firefox134:
--- → affected
Reverting bug 1925679's patch
https://phabricator.services.mozilla.com/D229170
| Assignee | ||
Comment 3•1 year ago
|
||
| Assignee | ||
Updated•1 year ago
|
Whiteboard: [fxdroid][group3][toolbar-redesign-beta-blocker]
Updated•1 year ago
|
Updated•1 year ago
|
Attachment #9438065 -
Attachment is obsolete: true
Fixed with the revert mentioned above
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Updated•1 year ago
|
Target Milestone: --- → 134 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•