<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi, <div><br></div><div>I really like the way Chrome presents a site's permission (apart from the issues that particular style raises), and I'd like to see something similar in Firefox. The mockup is a good starting point. However, I'd like to suggest a few modifications (and additions and clarifications), not only because the current mockup does not scale well to many permissions just like Chrome's style does: </div><div><br></div><div>1) In the identity panel, only display the permissions that have been set differently from the standard permissions. Optionally, display enabling permissions first (where the default disables a permission) and then list revoked permissions (where permissions for a site where not given whereas the standard setting allows those). Revoked permissions can overflow (those are less important than enabling permissions). Maybe extra permissions need to be overflown, too, depending on the number of explicitly set permissions (but I suspect nobody sets more than a dozen different permissions for a website but rather installs a Web App). </div><div><br></div><div>2) A "more" link shows overflown permissions inline, maybe even permissions equal to the standard permission set for easy en-/disabling of permissions. (The last situation occurs on any newly visited website thus it can be helpful to provide a non-comprehensive list of standard permissions that the user can set directly, e. g. cookies and password.)</div><div><br></div><div>3) Clicking on a permission (whereas "permission" is the permission icon in the mockup) opens a drop down where a user can select "allow always / temporarily / never" (wording TBD) with the standard being highlighted (bold text, added text "(default)"). </div><div>(TBD: What happens when a user selects "never" and the standard is "never" – is the permission setting removed from the database or not; the difference is when a user changes a default setting: Does the user expect to change the permissions for all sites to allow a feature even when he revoked an earlier explicit permission? I guess so, and that use case is seldom enough that IMO we can just remove a permission setting from a website when its permission is set back to the default value.)</div><div><br></div><div>4) A "show all permissions" link points to the respective <a href="about:permissions">about:permissions</a> entry where all possible permissions are listed. When there is no entry in the <a href="about:permissions">about:permissions</a> listing, it is automatically added to and later removed from the listing if all site permissions are reset to its default values (see No 5). </div><div><br></div><div>5) <a href="about:permissions">about:permissions</a> needs to be reworked (apart from a simple facelift). It should only (alphabetically or by-last-visit) list sites that have permissions explicitly set differently from the default values. Sites can be removed from the list (UI TBD, e. g. a "reset to defaults" button within the detail view, site is removed upon closing <a href="about:permissions">about:permissions</a>), which means their explicit permissions are reset to the respective default value. Sites can be added via the search feature which provides auto-completion with entries from the user's history (both URL and Titles can be used for searching/adding entries). </div><div><br></div><div>I meant to sketch a wireframe for a reworked <a href="about:permissions">about:permissions</a> UI, maybe I can do that this week to show you what I'd like to see there. </div><div><br></div><div>Concerning the identity panel and the mockup, the permissions area is indeed a bit small (whereas the encryption part is overly large, the size of the identity part is IMO fitting). Plus, using only icons for the permissions is (although easily skim-able) at best confusing for new user and at worst a huge PITA for feature developers (How can I visualize a Notification, a Simple Push etc. permission in a tiny icon in such a way it cannot be confused with other permissions? Plus, the user has to be able to remember what each icon means!). An icon only mode is probably desirable for power users and may be enabled via pref, but for most users, a (two column) list of permissions is probably better ("Differing from the default permissions, <a href="http://example.com">example.com</a> can * set Cookies temporarily / permanently / never, * save passwords, …"), each with button + triangle (button shape only visible on hover) for the drop down menu. </div><div><br></div><div>Does my explanation make sense or should I mockup that, too? </div><div><br></div><div><br></div><div><div apple-content-edited="true">
<div>Best regards,</div><div><br></div><div>Florian Bender</div><div><br></div><div><br></div><span style="font-size: 11px; ">quantumedia · Kalchthaler, Müller & Partner </span><span style="font-size: 11px; ">Media Services GbR</span><br style="font-size: 11px; "><span style="font-size: 11px; ">Münsterplatz 32 · 79098 Freiburg · Tel. 0761 </span><span style="font-size: 11px; ">458 99 28-0 · Fax 0761 458 99 28-9</span><br style="font-size: 11px; "><span style="font-size: 11px; ">USt-IdNr: DE280390014 · Geschäftsführer: </span><span style="font-size: 11px; ">Gregor Kalchthaler, Philipp Müller</span>
</div>
<br></div></body></html>