New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: work around ScreenCaptureKit bad feature flag parsing in Chromium #41622
Conversation
15d6e7e
to
a91d496
Compare
No Release Notes |
/trop run backport-to 30-x-y |
The backport process for this PR has been manually initiated - sending your PR to |
/trop run backport to 29-x-y |
I have automatically backported this PR to "30-x-y", please check out #41961 |
/trop run backport-to 29-x-y |
The backport process for this PR has been manually initiated - sending your PR to |
I have automatically backported this PR to "29-x-y", please check out #41962 |
Description of Change
Ref #41397.
Details
This works fine in release builds but bombs in testing because of the way feature flags are currently parsed:
To fix this for now and unblock local development on macOS 14.4, only set it in release.
Checklist
npm test
passesRelease Notes
Notes: none