Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(470)

Issue 2103653004: Revert of MD Settings: make chrome://[md-]settings/clearBrowserData URL work (Closed)

Created:
4 years, 5 months ago by shans
Modified:
4 years, 5 months ago
Reviewers:
Dan Beam, michaelpg
CC:
chromium-reviews, michaelpg+watch-md-settings_chromium.org, michaelpg+watch-md-ui_chromium.org, dbeam+watch-settings_chromium.org, stevenjb+watch-md-settings_chromium.org, arv+watch_chromium.org, tommycli
Base URL:
https://chromium.googlesource.com/chromium/src.git@master
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

Revert of MD Settings: make chrome://[md-]settings/clearBrowserData URL work (patchset #7 id:120001 of https://codereview.chromium.org/2094223004/ ) Reason for revert: Looks like this is causing CrSettingsPrivacyPageTest.PrivacyPage to fail on Mac10.9 and Mac ASAN Original issue's description: > MD Settings: make chrome://[md-]settings/clearBrowserData URL work > > R=michaelpg@chromium.org > BUG=622037 > CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation > > Committed: https://crrev.com/a6ecac07f74cf819dc164bb91f721e596c261cd2 > Cr-Commit-Position: refs/heads/master@{#402614} TBR=michaelpg@chromium.org,dbeam@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=622037 Committed: https://crrev.com/6000aea80c445f9932dcdbbe53d8f963f7a3182f Cr-Commit-Position: refs/heads/master@{#402651}

Patch Set 1 #

Total comments: 3

Messages

Total messages: 10 (2 generated)
shans
Created Revert of MD Settings: make chrome://[md-]settings/clearBrowserData URL work
4 years, 5 months ago (2016-06-29 01:48:01 UTC) #2
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2103653004/1
4 years, 5 months ago (2016-06-29 01:50:05 UTC) #3
michaelpg
lgtm but :'( dbeam, can you poke at this some more? https://codereview.chromium.org/2103653004/diff/1/chrome/browser/resources/settings/privacy_page/privacy_page.js File chrome/browser/resources/settings/privacy_page/privacy_page.js (left): ...
4 years, 5 months ago (2016-06-29 01:54:40 UTC) #4
commit-bot: I haz the power
Committed patchset #1 (id:1)
4 years, 5 months ago (2016-06-29 02:00:12 UTC) #5
commit-bot: I haz the power
Patchset 1 (id:??) landed as https://crrev.com/6000aea80c445f9932dcdbbe53d8f963f7a3182f Cr-Commit-Position: refs/heads/master@{#402651}
4 years, 5 months ago (2016-06-29 02:02:47 UTC) #7
Dan Beam
https://codereview.chromium.org/2103653004/diff/1/chrome/browser/resources/settings/privacy_page/privacy_page.js File chrome/browser/resources/settings/privacy_page/privacy_page.js (left): https://codereview.chromium.org/2103653004/diff/1/chrome/browser/resources/settings/privacy_page/privacy_page.js#oldcode43 chrome/browser/resources/settings/privacy_page/privacy_page.js:43: settings.main.rendered.then(function() { On 2016/06/29 01:54:40, michaelpg wrote: > Haha, ...
4 years, 5 months ago (2016-06-29 20:42:50 UTC) #8
Dan Beam
On 2016/06/29 20:42:50, Dan Beam wrote: > https://codereview.chromium.org/2103653004/diff/1/chrome/browser/resources/settings/privacy_page/privacy_page.js > File chrome/browser/resources/settings/privacy_page/privacy_page.js (left): > > https://codereview.chromium.org/2103653004/diff/1/chrome/browser/resources/settings/privacy_page/privacy_page.js#oldcode43 ...
4 years, 5 months ago (2016-06-29 20:42:59 UTC) #9
michaelpg
4 years, 5 months ago (2016-06-29 21:03:30 UTC) #10
Message was sent while issue was closed.
https://codereview.chromium.org/2103653004/diff/1/chrome/browser/resources/se...
File chrome/browser/resources/settings/privacy_page/privacy_page.js (left):

https://codereview.chromium.org/2103653004/diff/1/chrome/browser/resources/se...
chrome/browser/resources/settings/privacy_page/privacy_page.js:43:
settings.main.rendered.then(function() {
On 2016/06/29 20:42:49, Dan Beam wrote:
> On 2016/06/29 01:54:40, michaelpg wrote:
> > Haha, I guess that's what happens when you suppress missing properties :-P
> 
> tests aren't compiled

I didn't mean to imply causality per se. "And that's why you don't suppress
closure warnings."

> 
> > 
> > [16721:1287:0628/183642:ERROR:CONSOLE(44)] "Mocha test failed:
> > NativeCertificateManager "before each" hook
> > Error: Uncaught TypeError: Cannot read property 'rendered' of undefined
> > (privacy_page.js:43)
> >     at Context.<anonymous> (privacy_page_test.js:78:23)
> > ", source: mocha_adapter.js (44)
> > 
> > privacy_page_test.js (via cr_settings_browsertest.js) loads
privacy_page.html
> > which of course doesn't import settings-main, so this fails
> 
> our we just not running our tests on try runs?  this is like the second or
third
> time something hasn't been caught by the try bots.

Powered by Google App Engine
This is Rietveld 408576698