New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 775857 link

Starred by 2 users
Status: Fixed
Owner:
paulir...@chromium.org
Closed: Sep 4
Cc:
█ krajshree@chromium.org
ajha@chromium.org
█ brajkumar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Unable to run an audit for the second time

Project Member Reported by kebalaji@chromium.org, Oct 18 2017 
Chrome Version: 62.0.3202.63/9901.49.0 beta-channel Daisy,Candy and Reks
OS: Chrome OS


What steps will reproduce the problem?
(1)Sign into user >> Open devtools in NTP
(2)Click on perform an audit and run an audit >> Cancel it and close the dialog box >> Again try running an audit and observe

Expected:should be able to run an audit
Actual: Instead, unable to run an audit

This is Regression issue as same is working fine in M-59(Old Audits UI) 

@paulirish : Please confirm the issue

Note:
1.Issue is seen in latest M-64 also
2.Issue is not applicable to Windows & Linux OS
AuditsActual.webm
800 KB View Download

Comment 1 by sjoer...@gmail.com, Nov 27 2017 

I have the same issue in Version 62.0.3202.94 (Official Build) Built on Ubuntu , running on Ubuntu 16.04 (64-bit).

The "Auditing your web page ..." dialog shows forever. Clicking cancel changes "Loading..." into "Cancelling...", but the dialog doesn't disappear. If you click the X, the dialog closes. After that, the "Run audit" and "Cancel" buttons no longer work.

Comment 2 by navr...@gmail.com, Dec 11 2017 

I am experiencing the same problem on Windows 7

Version 63.0.3239.84 (Official Build) (64-bit)

Installed from http://chromium.woolyss.com/f/chrlauncher-win64-stable-codecs-sync.zip

Click on "Perform an audit..."
- Loading... Spinner
- "Device toolbar >> Nexus 5X" is toggled
- Cancel and Close buttons do not work

Comment 3 by paulir...@chromium.org, Sep 4

Status: Fixed (was: Assigned)
I believe this is fixed as of may 2018. 

Please let me know if you can still reproduce this buggy behavior.
►

Sign in to add a comment