Page MenuHomePhabricator

Make "No Notifications" setting less broad, and fix a bug with default display behavior
ClosedPublic

Authored by epriestley on Sep 13 2017, 9:59 PM.
Tags
None
Referenced Files
F14096768: D18600.diff
Tue, Nov 26, 5:06 AM
F14096716: D18600.diff
Tue, Nov 26, 4:56 AM
Unknown Object (File)
Sun, Nov 24, 8:51 AM
Unknown Object (File)
Fri, Nov 22, 11:41 PM
Unknown Object (File)
Thu, Nov 21, 7:00 PM
Unknown Object (File)
Mon, Nov 18, 11:14 AM
Unknown Object (File)
Thu, Nov 14, 1:21 AM
Unknown Object (File)
Mon, Nov 11, 5:58 AM
Subscribers
None

Details

Summary

Fixes T12979. In D18457, we added a "No Notifications" setting to let users disable the blue and yellow pop-up notifications that alert you when an object has been updated, since some users found them distracting.

However, the change made "do nothing" the default, so all other JX.Notification callsites -- which never pass a preference -- were effectively turned off no matter what your setting was set to. This includes the "Read-Only" mode warning (grey), the "High Security" mode warning (purple), the "timezone" warning, and a few others.

Tweak things a little bit so the setting applies to ONLY blue and yellow ("object you're following was updated" / "this object was updated") notifications, not other types of popup notifications.

Test Plan
  • With notifications on in settings, got blue notifications and "Read-only".
  • With notifications off in settings, got "Read-only" but no blue notifications.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

src/applications/notification/builder/PhabricatorNotificationBuilder.php
174–176

Er, I think these are probably not wrong exactly but the old version was clearer, I'll use something more similar.

  • Use slightly clearer construction in NotificationBuilder.
This revision is now accepted and ready to land.Sep 13 2017, 10:09 PM