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

Issue 4552: Restore features to correct state after disabling field trials #2471

Merged
merged 5 commits into from
May 29, 2019

Conversation

jumde
Copy link
Contributor

@jumde jumde commented May 21, 2019

Fix brave/brave-browser#4552

Submitter Checklist:

Test Plan:

  1. Navigate to https://www.globalsign.com/en/ and verify if a lock is displayed instead of a Secure Chip

Secure Chip:
Screen Shot 2019-05-21 at 1 03 20 PM

Lock Only:
Screen Shot 2019-05-21 at 1 12 12 PM

Reviewer Checklist:

  • New files have MPL-2.0 license header.
  • Request a security/privacy review as needed.
  • Adequate test coverage exists to prevent regressions
  • Verify test plan is specified in PR before merging to source

After-merge Checklist:

  • The associated issue milestone is set to the smallest version that the
    changes has landed on.
  • All relevant documentation has been updated.

@jumde jumde self-assigned this May 21, 2019
@jumde jumde force-pushed the disable_field_trials branch from ce050d4 to 8a0447f Compare May 21, 2019 21:28
@jumde jumde changed the title WIP - Issue 4283: Disable field trials Issue 4283: Disable field trials May 21, 2019
@jumde jumde changed the title Issue 4283: Disable field trials Issue 4283: Disable field trials + Display lock for all HTTPS sites (including sites with EV certs) May 21, 2019
@simonhong
Copy link
Member

simonhong commented May 22, 2019

I think some of enabled/disabled features by us in BraveMainDelegate::BasicStartupComplete can be deleted.(ex, kLookalikeUrlNavigationSuggestionsUI is disabled by default but enabled by field trials)
FYI, BraveMainDelegateBrowserTest.DisabledFeatures would be useful for testing this change.
Also, it would be nice to add test for enabled features we override.

@simonhong
Copy link
Member

simonhong commented May 22, 2019

How about splitting this into two PRs(or commits)?
One is disabling field trials and the other is for ev certs.

@simonhong simonhong self-requested a review May 22, 2019 11:01
@jumde
Copy link
Contributor Author

jumde commented May 22, 2019

How about splitting this into two PRs(or commits)?
One is disabling field trials and the other is for ev certs.

@simonhong - HttpsIndicatorParameterBothToLock is the current behavior of the HTTPS indicator in the release channels. Disabling Field Trials was setting this back to EvToSecure which is not desired per the product requirements, so I merged the change into a single PR to avoid regressions from disabling field trials.

@jumde jumde force-pushed the disable_field_trials branch from 8a0447f to 522b68b Compare May 22, 2019 20:49
};

// Disabled features.
const std::unordered_set<const char*> disabled_features = {
autofill::features::kAutofillSaveCardSignInAfterLocalSave.name,
autofill::features::kAutofillServerCommunication.name,
features::kAudioServiceOutOfProcess.name,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removing since this feature is disabled by default. https://cs.chromium.org/chromium/src/content/public/common/content_features.cc?l=51

The test in to check if this feature is disabled is still available in brave_main_delegate_browsertest.cc to alert if this feature gets enabled in future. cc: @darkdh @mkarolin

};

// Disabled features.
const std::unordered_set<const char*> disabled_features = {
autofill::features::kAutofillSaveCardSignInAfterLocalSave.name,
autofill::features::kAutofillServerCommunication.name,
features::kAudioServiceOutOfProcess.name,
features::kDefaultEnableOopRasterization.name,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

network::features::kNetworkService.name,
unified_consent::kUnifiedConsent.name,
features::kLookalikeUrlNavigationSuggestionsUI.name,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jumde jumde force-pushed the disable_field_trials branch 2 times, most recently from 1488acd to df516a6 Compare May 23, 2019 05:12
# TODO(thakis): It's strange this is called "_like_official_build" but then
# checks is_chrome_branded, not is_official_build.
- fieldtrial_testing_like_official_build = is_chrome_branded
+ fieldtrial_testing_like_official_build = true
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of modifying args here, overriding it from config.js would be better.

IN_PROC_BROWSER_TEST_F(SecurityIndicatorTest, CheckIndicatorText) {
const GURL kMockNonsecureURL =
embedded_test_server()->GetURL("example.test", "/");
const base::string16 kEmptyString = base::string16();
Copy link
Member

@simonhong simonhong May 23, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fyi: there is base::EmptyString16().

@jumde jumde changed the title Issue 4283: Disable field trials + Display lock for all HTTPS sites (including sites with EV certs) Issue 4552: Restore features to correct state after disabling field trials May 23, 2019
@jumde jumde force-pushed the disable_field_trials branch from 3b8dd20 to 1fadff3 Compare May 23, 2019 15:35
@diracdeltas
Copy link
Member

note for release managers: this needs to be in the same release as brave/brave-browser#4551

@jumde jumde force-pushed the disable_field_trials branch 5 times, most recently from 3f1896c to dc56bfd Compare May 24, 2019 15:19
namespace {
typedef testing::Test FieldTrialsTest;

TEST_F(FieldTrialsTest, FieldTrialsTestingEnabled) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we also verify that field trial downloads are disabled?

@jumde jumde force-pushed the disable_field_trials branch from dc56bfd to 58a37c5 Compare May 24, 2019 20:27
@bridiver bridiver mentioned this pull request May 28, 2019
19 tasks
darkdh added a commit that referenced this pull request May 28, 2019
@jumde jumde merged commit cda823c into master May 29, 2019
@bsclifton bsclifton deleted the disable_field_trials branch May 29, 2019 21:45
@bsclifton bsclifton added this to the 0.68.x - Nightly milestone May 29, 2019
@bsclifton
Copy link
Member

bsclifton commented May 29, 2019

Updated this PR, brave/brave-browser#4551, and both issues (brave/brave-browser#4283 and brave/brave-browser#4552) to have the 0.68.x milestone 😄👍

Also added release-notes/include tag to them (if we don't want to note that in release notes, feel free to change to exclude, @jumde)

darkdh added a commit that referenced this pull request May 30, 2019
darkdh added a commit that referenced this pull request May 30, 2019
darkdh added a commit that referenced this pull request May 31, 2019
darkdh added a commit that referenced this pull request Jun 18, 2019
darkdh added a commit that referenced this pull request Jul 16, 2019
darkdh added a commit that referenced this pull request Jul 18, 2019
darkdh added a commit that referenced this pull request Jul 23, 2019
darkdh added a commit that referenced this pull request Aug 9, 2019
darkdh added a commit that referenced this pull request Aug 9, 2019
darkdh added a commit that referenced this pull request Aug 15, 2019
darkdh added a commit that referenced this pull request Aug 19, 2019
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.

Revert features to correct state after disabling field trials
5 participants