Details on Product UI Security

All Issues

New issues for this product are notified to bigassboy53245@gmail.com (change it).

There are 12 issues listed in the system.

ID	State	Title	Raised on	Product	Open Actions
ISSUE-20	CLOSED	If browsers apply UI Security heuristic without an explicit opt-in policy, should we always block and not have the unsafe UIEvent property	2012-11-01	UI Security	0
ISSUE-25	CLOSED	Do frame-options directives (or other UISafety directives) make sense in a meta tag context?	2012-11-01	UI Security	0
ISSUE-27	CLOSED	Implementation concern on how to enforce display-time : should we provide more advice on how to do this efficiently?	2012-11-01	UI Security	0
ISSUE-45 'top-only'	CLOSED	Is 'top-only' worth preserving?	2013-03-05	UI Security	0
ISSUE-52 unsafe DOM API	CLOSED	unsafe attribute requires every handler to check	2013-04-25	UI Security	0
ISSUE-53 UI Security model for composited drawing models	CLOSED	UI Security model for composited drawing models	2013-04-26	UI Security	0
ISSUE-55 input-protection and seamless iframes	CLOSED	How to handle seamless flag for input-protection policies?	2013-10-31	UI Security	0
ISSUE-5	PENDING REVIEW	Is covering identical UI with different effects in-scope? e.g. "like" button that doesn't indicate what you're liking	2011-11-01	UI Security	0
ISSUE-22	PENDING REVIEW	Are there cases of synthetic UIEvents where it would be useful to set the unsafe attribute even if the policy is block (so event is not delivered)	2012-11-01	UI Security	0
ISSUE-28	PENDING REVIEW	What specific attacks are prevented by OS screenshots, should this be recommended against generally?	2012-11-01	UI Security	0
ISSUE-29	PENDING REVIEW	What are sane defaults for clipping with clipping or selectors?	2012-11-01	UI Security	0
ISSUE-21	POSTPONED	Do assistive technologies send real events or synthetic events?	2012-11-01	UI Security	0

All Actions

There are 0 actions.

Add a new action item.

See only open and raised issues and actions.