Yeah, I understood :) I haven't seen much discussion of these issues so figured I'd try and start some - perhaps a lurker would be motivated to work on it. Or maybe the Chrome team in a later release.
The force-ssl stuff seems like good progress. Still, Chrome takes a less aggressive stance than Firefox on things like click-through warnings and that doesn't seem like needing academic study to resolve. On Nov 3, 4:56 am, Adam Barth <aba...@chromium.org> wrote: > I'm sorry if my email came off as dismissive. I really would like to > see some serious study of user interfaces for certificate errors. I > think everyone agrees that the current designs can be improved. We > even know how to measure success > (e.g.,http://www.usenix.org/events/sec09/tech/full_papers/sunshine.pdf). > What we don't know is how to design something measurably better. > > Adam > > > > On Mon, Nov 2, 2009 at 6:19 PM, Evan Stade <est...@chromium.org> wrote: > > I now have a new response ready for the next "click to select all" thread: > > > "the best way to make your case is to write an academic paper and > > conduct a user study that shows how the new UI out-performs the > > current UI." > > > -- Evan Stade --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
