Issue metadata
Sign in to add a comment
|
Merge ChooserContext with PermissionContext |
||||||||||||||||||||||
Issue descriptionWe should consider merging ChooserContext and PermissionContext so that we have the same codepaths for permission logic (to minimise duplication, avoid policy violations, etc.) jyasskin: were you still interested in looking at this?
,
Mar 10 2016
,
Mar 12 2016
Yes, I'm still interested in looking at this. I'm working on the Permissions API update first, at https://github.com/w3c/permissions/pull/66, so that we have a better idea what the PermissionContext API ought to be, before I start refactoring it.
,
Mar 14 2016
Great, thanks!
,
Nov 22 2016
,
Nov 29 2016
,
Jun 2 2017
,
Nov 10 2017
,
Feb 18 2018
,
Oct 11
Raymes, would you still encourage us to make this change?
,
Oct 14
Yes I think it's still something worth investigating but not urgent. The main reason would be to ensure that we don't duplicate checks between choosers and regular permissions and that both are subject to the same constraints. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by benwells@chromium.org
, Mar 9 2016