[Re-enable] policy_CookiesSessionOnlyForUrls depends on chrome://settings-frame |
|||||||||
Issue descriptionchrome://setttings-frame is going away in M-60. We should not be relying on Chrome UI for autotest. Please convert policy_CookiesSessionOnlyForUrls to use the chrome.autotestPrivate API or another chrome API instead. (Otherwise we will need to disable the test) See https://chromium-review.googlesource.com/#/c/470707/ for an example ( issue 694081 ).
,
Apr 18 2017
,
Apr 18 2017
,
May 23 2017
Reminder: This test will break (and be disabled) if not fixed for M-60. The problematic code is here: https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/client/site_tests/policy_CookiesSessionOnlyForUrls/policy_CookiesSessionOnlyForUrls.py?q=chrome://settings+package:%5Echromeos_public$&l=48
,
May 23 2017
Katherine has added a bunch of autotestPrivate apis for a11y and should be able to provide advice here on how to do this.
,
Jul 24 2017
What is the status of this? chrome://settings-frame is being actively deprecated now. It is only semi-functional in 61.
,
Jul 28 2017
Pri-0 bugs are critical regressions or serious emergencies, and this bug has not been updated in three days. Could you please provide an update, or adjust the priority to a more appropriate level if applicable? If a fix is in active development, please set the status to Started. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 28 2017
Note: chrome://settings-frame has been removed from ToT chrome, so any attempts to run it will fail once Chrome uprevs (i.e. once the PFQ succeeds). I do not see any current references to it so I assume it is only run by manually, if at all.
,
Jul 28 2017
,
May 7 2018
,
May 7 2018
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by krishna...@chromium.org
, Apr 18 2017