Skip to content
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

fix: Improve --enable-features/--disable-features handling (2.0.x) #13921

Merged
merged 1 commit into from
Aug 3, 2018

Conversation

poiru
Copy link
Contributor

@poiru poiru commented Aug 2, 2018

As it turns out, we can reinitialize the feature list directly after the
user JS script has been executed instead of much later. This allows
modifications to --enable-features/--disable-features to work with a
greater set of features.

This backports #13920 to 2-0-x.

As it turns out, we can reinitialize the feature list directly after the
user JS script has been executed instead of much later. This allows
modifications to `--enable-features`/`--disable-features` to work with a
greater set of features.

This backports #13920 to `2-0-x`.
@poiru poiru requested a review from a team August 2, 2018 21:06
@MarshallOfSound
Copy link
Member

@poiru We normally let the bot do the backporting so that this goes to all appropriate release lines. Gonna close this out but will re-visit if the bot fails to backport your master PR

@MarshallOfSound MarshallOfSound merged commit dffd17a into 2-0-x Aug 3, 2018
@MarshallOfSound MarshallOfSound deleted the reinit-feature-list-sooner-2-0-x branch August 3, 2018 01:09
@daviwil daviwil mentioned this pull request Aug 9, 2018
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants