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
..
css	Distinguish between invalid/broken handles and filtered handles	2013-10-17 10:49:21 -07:00
externals	Add a synthetic DOM event to JX.Workflow for form submission	2013-10-14 11:58:38 -07:00
image	White policy icons	2013-10-17 07:41:02 -07:00
js	Add an icon+background selector for project images	2013-10-17 09:32:34 -07:00
swf	Remove spurious "+x" from files that shouldn't have it	2013-10-05 05:18:17 -07:00