Issue metadata
Sign in to add a comment
|
Regression:Enabling/Disabling any flag under chrome flags and relaunching chrome disables the new MDRefresh UI
Reported by
vineetha...@etouch.net,
Aug 1
|
||||||||||||||||||||||
Issue descriptionChrome Version: 69.0.3497.23 (Official Build) Revision a0f931c424245a817bf2ad63eb45c6c95f28e1ee-refs/branch-heads/3497@{#301}(64 bit) OS:Windows(7,8,8.1,10) What steps will reproduce the problem? (1) Freshly launch Chrome, navigate to chrome://flags. (2) Enable/Disable any flag and relaunch browser, now observe the UI. Actual Result : Enabling/Disabling any flag under chrome flags and relaunching chrome disables the new MDRefresh UI. Expected Result: New MDRefreshUI should be seen even after enabling/disabling any flag under chrome flags and relaunching chrome. This is regression issue broken in ‘M-69’: (Unable to provide bisect using per-revision since getting error while bisecting and in narrow bisect issue is not reproducible on chromium builds , hence providing bisect manually) Good build: 69.0.3497.0(Revision: 576754) Bad build : 70.0.3498.0(Revision: 577006) Suspect: r576966 ? @robliao: Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. Note: 1)Issue is also seen on current Dev build #69.0.3497.12 and latest Canary build #70.0.3508.0 2)Issue was not seen on build #70.0.3508.0 till yesterday. Thank You!
,
Aug 1
,
Aug 2
Update w.r.t comment #1: As mentioned, kindly refer the attached screenshot showing the variation list. Note: Just to update, the above issue is not flag specific and happens when the browser is relaunched. Thank you!
,
Aug 8
Issue 872274 has been merged into this issue.
,
Aug 14
The behavior as stated is intended. If there is more data, feel free to reopen. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by robliao@chromium.org
, Aug 1