You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like the whole elevated consent process, or "Application Permission" is going to be interesting. While Chrome/Blink has decided to go for an application install process, it's likely that Firefox will not.
I think that we need to abstract a little more and just say that there is some special process that is required to grant a site the ability to share the browser.
The text was updated successfully, but these errors were encountered:
By "Application Permission" do you mean the fundamental rights of the application to be able to share? I can understand the level of control that an application install process can offer although it does not alone fully mitigate the risk of a rogue app requesting share. An application install process also imposes a level of additional requirement on a share based web app that may not be desirable. Some definition of this process will be needed to state conditions under which a site/app can share.
I think that for the most part browser UX people will be able to make the right decision. The key here is not to focus on the specifics of the authorization process, but to highlight the importance of it and to note that anything that might be trivially clicked through is generally not sufficient.
Looks like the whole elevated consent process, or "Application Permission" is going to be interesting. While Chrome/Blink has decided to go for an application install process, it's likely that Firefox will not.
I think that we need to abstract a little more and just say that there is some special process that is required to grant a site the ability to share the browser.
The text was updated successfully, but these errors were encountered: