New issue
Advanced search Search tips

Issue 833966 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

disable download nag on every file

Reported by johnysmy...@gmail.com, Apr 17 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.20.6530.0 Safari/537.36

Steps to reproduce the problem:
1. the nag appears on every file
2. I use chrome(not chromium) and this does not happen
3. 

What is the expected behavior?
the nag message should not appear

What went wrong?
look at the jpg i uploaded here. I do not want to see this nag message every time I download a file. How to disable it?

I don't want to lose any other protection if I don't have to.

Did this work before? N/A 

Chrome version: 54.20.6530.0  Channel: n/a
OS Version: 5.1 (Windows XP)
Flash Version: Shockwave Flash 99.0 r0
 
nag.jpg
9.7 KB View Download
Can you please update your browser? You are using a very out-of-date version of Chrome that isn't supported anymore.
Components: UI>Browser>Downloads
Labels: Needs-Feedback
Labels: Needs-Milestone
this never worked before. I am using windows XP. I was under the impression that I was using the latest version and it was supported. (which is why I downloaded it in the first place)


this never worked before. I am using windows XP. I was under the impression that I was using the latest version and it was supported. (which is why I downloaded it in the first place)


Project Member

Comment 6 by sheriffbot@chromium.org, Apr 18 2018

Cc: dtapu...@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Unconfirmed)
Looks like you're using version 54 which is really out of date.  If Chrome doesn't upgrade on XP there's no way we can fix this.  It sounds like it's already fixed on the latest version of Chrome (65).

Sign in to add a comment