Page MenuHomePhabricator

FlaggedRevs popup is overly intrusive
Closed, DuplicatePublicBUG REPORT

Assigned To
None
Authored By
Xaosflux
Sep 16 2024, 10:32 AM
Referenced Files
F57515202: image.png
Sep 16 2024, 3:17 PM
F57514557: image.png
Sep 16 2024, 10:41 AM
F57514549: image.png
Sep 16 2024, 10:32 AM

Description

Steps to replicate the issue (include links if applicable):

  • Got to a page with pending changes
  • Purposefully, or incidentally hover the large "() PENDING" section of the header

What happens?:

  • A popup screen is loaded
  • The popup screen is persistent until manually cleared, obscuring page content

What should have happened instead?:

  • The popup screen loaded from hover should only persist while being hovered

Software version (on Special:Version page; skip for WMF-hosted wikis like Wikipedia):
WMF production
Other information (browser name/version, screenshots, etc.):
https://en.wikipedia.org/wiki/Alien_(franchise)

image.png (422×511 px, 23 KB)

Event Timeline

At the very least perhaps this should require an unclick instead of an onhover, as attempting to hover any of the other indicators in the area is likely to lead to continual popups of flagrevs even if you have no desire to use that function at the moment.

For example, oops don't stray a few pixels from trying to use the coordinators indicator:

POP UP!

image.png (317×430 px, 16 KB)

<gripe>Prehaps - ticket may be another victim of our lack of an incident management system.... </gripe>

@Tufor (see image below) - however if you are referring to how it looks when it is NOT poped-up, that should be a different bug report (I agree it looks really bad there, as in the image below)

image.png (126×344 px, 7 KB)

<gripe>Prehaps - ticket may be another victim of our lack of an incident management system.... </gripe>

What does that mean?

(Straying off topic of this ticket which if it is a duplicate should certainly be merged in)

@Aklapper Short summary of my gripe: In many cases when someone discovers a problem and reports it to Phabricator, their ticket will get resolved prior to the problem actually being remedied in production. The normal defense is that Phab isn't an incident management tracker, the counter argument is that maybe it should be. See https://meta.wikimedia.org/wiki/Community_Wishlist/Wishes/Centralized_Incident_Management for the long version of this, revisited.

This should be fixed on Thursday. Sorry for any inconvenience.