phorge/src
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
..
aphront Fix breadcrumbs for login screen triggered when a logged-out user fails a policy check 2013-10-14 11:46:26 -07:00
applications Distinguish between invalid/broken handles and filtered handles 2013-10-17 10:49:21 -07:00
docs Convert maniphest to use standard fields 2013-09-19 11:56:15 -07:00
extensions Add src/extensions/ to Phabricator 2013-08-14 15:38:06 -07:00
infrastructure Distinguish between invalid/broken handles and filtered handles 2013-10-17 10:49:21 -07:00
view Add an icon+background selector for project images 2013-10-17 09:32:34 -07:00
__celerity_resource_map__.php Distinguish between invalid/broken handles and filtered handles 2013-10-17 10:49:21 -07:00
__phutil_library_init__.php
__phutil_library_map__.php Add an icon+background selector for project images 2013-10-17 09:32:34 -07:00