1
0
Fork 0
mirror of https://we.phorge.it/source/phorge.git synced 2024-11-23 07:12:41 +01:00
phorge-phorge/webroot/rsrc/css/application/base
epriestley 95c2b03fc8 Distinguish between invalid/broken handles and filtered handles
Summary:
Ref T603. Currently, we render handles the user doesn't have permission to see in a manner identical to handles that don't exist. This is confusing, and not required by policies (which restrict content, but permit knowledge that an object exists).

Instead, render them in different styles. Bad/invalid objects look like:

  Unknown Object (Task)

Restricted objects look like:

  [o] Restricted Task

...where `[o]` is the padlock icon.

Test Plan:
{F71100}

{F71101}

It's possible this renders weird somewhere, but I wasn't immediately able to find any issues. Yell if you see something.

Reviewers: btrahan, chad

Reviewed By: btrahan

CC: chad, aran

Maniphest Tasks: T603

Differential Revision: https://secure.phabricator.com/D7334
2013-10-17 10:49:21 -07:00
..
main-menu-view.css Move #888 and #999 to $lightgreytext 2013-09-02 08:12:18 -07:00
notification-menu.css Move #888 and #999 to $lightgreytext 2013-09-02 08:12:18 -07:00
phabricator-application-launch-view.css Fix hovers on mobile menus. 2013-06-12 10:30:15 -07:00
standard-page-view.css Distinguish between invalid/broken handles and filtered handles 2013-10-17 10:49:21 -07:00