<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; ">Nice!<div><br></div><div>Comments, some of which are kinda core semantics, so I'll dive in despite the edge case caveat:<div><br></div><div> I'd say "on this page", rather than "on the page", especially if this is a one-time deal. But both wordings are in conflict with "Trust Site", so there needs to be some clarification there: if I click "Trust Site", is every page on <a href="http://gaming.com">gaming.com</a> allowed to run Flash, or just this page? In other words, is "Trust Site" actually "Always allow this page to run Flash plugins", or "Always allow <a href="http://gaming.com">gaming.com</a> pages to run Flash plugins"?</div><div><br></div><div> There's a multiple-entry problem here. If I allow <a href="http://gaming.com">gaming.com</a> to use Silverlight, and next time I visit it includes both a Silverlight plugin and a Flash plugin, what happens? Do I see the dialog again? Which boxes are checked if so? Perhaps we need a "Previously allowed" annotation to stop users accidentally undoing a previous election?</div><div><br></div><div> For insecure plugins, should we perhaps change the wording to be something like "Add a security exception", rather than "Trust site"? Not only is this deliberately discouraging, which I think is good here, but it also avoids the cognitive blurring of <i>well, this site is insecure, but Firefox is going to 'trust' it
</i>.</div><div><br></div><div> The doorhanger might benefit from a "You can change these settings in
" or "You can get back to this by
" note, because otherwise there's a terrifying finality to my choice, particularly if the wording is "Allow Once" (AND ONCE ONLY, PUNY HUMAN).</div><div><br></div><div>Hope that helps rather than muddies the waters :)</div><div><br></div><div>-R</div><div><br></div><div><br></div><div><div><div>On 3 Apr 2013, at 7:12 PM, Larissa Co <<a href="mailto:lco@mozilla.com">lco@mozilla.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
<div bgcolor="#FFFFFF" text="#000000">
Hi all,<br>
<br>
I've been trying to figure out what the arrow panel experience will
be for pages with different types of plugins on the page. <br>
<br>
<b>*These are edge cases</b>*, so I'm not so worried about having
the most elegant looking design. I just want something that the user
can understand, especially because most pages with multiple plugins
are malicious (or so Bsmedberg tells me).<br>
<br>
This is the best design I can think of, after multiple iterations:
<a class="moz-txt-link-freetext" href="http://cl.ly/image/2n272J2n2J1k">http://cl.ly/image/2n272J2n2J1k</a><br>
<br>
Let me know what you think, since this will inform the typical
case's design. More to come on a final-ish design for CtP later this
week.<br>
<br>
Thanks,<br>
Larissa<br>
</div>
_______________________________________________<br>firefox-dev mailing list<br><a href="mailto:firefox-dev@mozilla.org">firefox-dev@mozilla.org</a><br>https://mail.mozilla.org/listinfo/firefox-dev<br></blockquote></div><br></div></div></body></html>