Repository navigation
fix(firefox): correct publishing and resolve validation warnings - #169
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Firefox version creation returned HTTP 400 because release notes were sent as multipart data alongside the source archive. Submit source files first, then update release notes through a separate JSON request. Strict shell failure handling, visible HTTP error bodies, and validation checks prevent failed submissions from appearing successful.
Firefox builds also disable Vue static HTML stringification and replace its unused static-content insertion body with an explicit error. Disabling the compiler optimization alone leaves the innerHTML assignment in the bundle. The build transform checks Vue's AST and fails if the expected implementation changes; Chrome retains its existing compilation and runtime. Vue upgrades may require revisiting this transform.
The Firefox manifest declares the existing Mozilla GUID and required identity, authentication, financial/purchase, and website-content data categories. Minimum Firefox versions are 140 on desktop and 142 on Android so the browser provides built-in data consent. Chrome receives no Firefox manifest fields.
Validation:
🤖