Feature/configurable browser flags #269
Merged
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.
🚀 Feature: Browser Flag Customization
Overview
This PR adds an
excludeBrowserFlags
option that lets developers disable individual default Chromium flags when running Extension.js. It resolves #252, enabling easier testing of scrollbars, audio, and other features impacted by default flags.Background
Extension.js starts browsers with a set of flags that streamline extension development, but a few of them can block key scenarios:
Usage Example
Compatibility & Testing ✅
Backward-compatible – no breaking changes
Verified on Chrome, Firefox, Edge (Manifest V2 & V3)
No measurable performance impact during launch or reload
Benefits
Better DX – test scroll & audio natively, no hacks
Cleaner workflow – delete post-install flag‐removal scripts
Type-safe – full TS support & autocompletion
Extensible – pattern can cover more defaults later
Closes
Closes #252