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

Issue 753395 link

Starred by 2 users
Status: WontFix
Owner:
█ apaci...@chromium.org
no longer active
Closed: Oct 2017
Cc:
jbanavatu@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

"Report an issue" doesn't work when chrome://flags/#enable-md-feedback is enabled

Reported by fabianro...@googlemail.com, Aug 8 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce the problem:
1. Go to chrome://flags/#enable-md-feedback and click on "Enable".
2. Restart Chrome
3. Press Alt+Shift+I (or Menu->Help->"Report an issue...")
4. Click "Send".

What is the expected behavior?
Feedback gets sent

What went wrong?
Button plays animation, but window doesn't close and "Thanks for feedback" page doesn't open. Probably it doesn't send the feedback.

Did this work before? No 

Chrome version: 59.0.3071.115  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 26.0 r0

Without the flag it works normally. So it's not of concern for normal users for now, but should definitely be fixed before Material design gets released for everyone.

Comment 1 by andrewbr...@gmail.com, Aug 8 2017 

Broken for me to in 9765.16.0 (Official Build) dev-channel edgar DEV

Comment 2 by jbanavatu@chromium.org, Aug 11 2017

Cc: jbanavatu@chromium.org
Components: UI>Browser>ReportAnIssue
Labels: -Type-Bug hasbisect-per-revision M-62 OS-Linux Type-Bug-Regression
Owner: apaci...@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce on Windows-10 & 7,Ubuntu 14.04 using reported version #59.0.3071.115, latest stable #60.0.3112.90 and latest canary #62.0.3182.0.

Note: Unable to check this issue in Mac OS as Report an issue overlay is not seen after enabling #enable-md-feedback flag.

Manual bisect info: 
Good build:54.0.2825.0 (410913)
Bad build: 54.0.2826.0 (411209)

You are probably looking for a change made after 410954 (known good), but no later than 410955 (first known bad).

CHANGELOG URL:
https://chromium.googlesource.com/chromium/src/+log/4178c185640b37e621703ac415141ac7caae06f4..7ef2fc0dbea076597d474315e15bae6fffb12de8

From the CL above, assigning the issue to the concern owner 

apacible @ 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. 

Review-Url: https://codereview.chromium.org/2159323003

Thanks!

Comment 3 by apaci...@chromium.org, Oct 9 2017

Status: WontFix (was: Assigned)
This flag is being removed in a CL in review.

Comment 4 Deleted

Comment 5 by fabianro...@googlemail.com, Dec 2 2017 

This bug is still present in version 62.0.3202.94, the flag is also still there, despite the previous comment (which is almost 3 months old). When was it planned to remove this flag?
►

Sign in to add a comment