WordPress.org

Make WordPress Core

Opened 3 years ago

Last modified 3 months ago

#18530 new defect (bug)

Browser update dismiss setting ignored with JavaScript disabled

Reported by: hakre Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 3.2.1
Component: Administration Keywords: dev-feedback ux-feedback ui-feedback
Focuses: ui Cc:

Description

When working on a corporate desktop you can not update your browser. When freely deciding about when to upgrade you might not even want to upgrade.

Therefore a user setting has been introduced to remove the nag warning. E.g. my linux distro is perfectly ok with it's firefox and it's taken care of by the pacakager. For my OS, I have the latest version.

I needed to press dismiss (with JS enabled, the related report is #17766).

What has been missed is to not display that nag if javascript is disabled. The setting gets ignored.

How to Reproducde

  • Setup a WP 3.2.1 Blog.
  • Log into admin with a Firefox 3 browser.
  • Enable Javascript.
  • Dismiss the Nag.
  • Logout and close the Browser.
  • Restart the Browser.
  • Disable Javascript (if you need to).
  • Log into Dashboard.

Result: Browser Update Nag is displayed.

Expected Result: Browser Update Nag is not displayed as specified by the user.

Change History (7)

comment:1 hakre3 years ago

  • Component changed from General to UI

comment:2 johnbillion3 years ago

  • Keywords reporter-feedback added

You mentioned #17766 in your ticket. How is this different?

comment:3 hakre3 years ago

@johnbillion: That ticket is about the dismiss button which is missing when javascript is disabled. This ticket is about ignoring the dismiss action. Both is an UI issue related to the same feature and javascript (so pretty close), but the nature of the report differs. In this report it was disabled but is displayed. In the other ticket the option to even disable is missing.

I've read that #17766 is about that it can't be disabled. Am I too nit-picky here? What do you think? Maybe it gets more traction if both issues are merged. Feel free to add additional defect to the other ticket if you think it's more appropriate. With one fix both issues could be closed anyway I think (at least chances are good). I had cross-reference both already.

Last edited 3 years ago by hakre (previous) (diff)

comment:4 hakre3 years ago

  • Keywords developer-feedback ux-feedback ui-feedback added; reporter-feedback removed

comment:5 SergeyBiryukov3 years ago

  • Keywords dev-feedback added; developer-feedback removed

comment:6 DrewAPicture15 months ago

  • Component changed from UI to Administration

comment:7 jeremyfelt3 months ago

  • Focuses ui added
Note: See TracTickets for help on using tickets.