Ok so where are we? Is there any agreement we can reach about _what_ I am trying to achieve? For the password manager, I want to fix my multiple login scenario with Google Apps, and support the multiple stage bank login scenario. For bookmarks, switching from mouse to keyboard every time is a large inconvenience! I am surprised you advocate this after saying moving your focus from the web page to the browser chrome to autologin is an issue.
How it is achieved is a matter of personal taste and as program designer, effort should be made to accommodate everyone! User's must be willing to learn new ways of working as they are trialling your new browser, but the new way can't be too inconvenient for them. > "Challenging user perceptions is rarely a better idea than working with them." The perception I am challenging is yours (as the browser author)! Password filling IS form filling. To reiterate where my idea differs from the current code is I will store details of the form like URL, field names (not just a username and password, but many fields) and the submit details as well as the values. In most circumstances once a login page is written the field names will only change occasionally. This plus allowing the user to choose which set of stored values (passcard) are used on a page are two benefits in terms of usability and reliability of my auto-login system. My proposal will support more complex auto-login situations and multi stage systems that the existing system cannot. To address your downside of moving from Submit in the webpage to the Chrome maybe we could look at other ways to present the auto fill system controller (maybe a popup or extend the Submit button you currently click)? Could you perhaps suggest another way of addressing the shortcomings I have highlighted? Reading the bug system I know I am not alone!! My idea about the star button could be done without change the existing UI, it is adding a function. Your comment about bookmarks is surprising! Maybe in your sample the majority do not use bookmarks, but an awful lot of people do! Moving from the mouse to the keyboard is something I rarely do when surfing (reading) and is a serious inconvenience! Please let me have an option to work without the bookmark bar! Were you saying No to both my ideas for changes to the star button, or just to swapping the current function to a long click? Chris On Oct 21, 12:34 am, "Peter Kasting" <[EMAIL PROTECTED]> wrote: > On Mon, Oct 20, 2008 at 4:21 PM, Chris G <[EMAIL PROTECTED]> wrote: > > On Oct 20, 6:29 pm, "Peter Kasting" <[EMAIL PROTECTED]> wrote: > > > I didn't mean that they were different HTML (although they can be), but > > > rather that users perceive them as having different functions. > > > This perception is what I (we) should challenge!! > > Challenging user perceptions is rarely a better idea than working with them. > > > I am totally willing to learn a new way of how to do what I need, > > But most users are not. > > So to cope without typing, > > Why rule out typing? I can type a single character and hit enter faster > than I can target a bookmark. > > Perhaps this is a good example of turnabout: _my_ normal workflow (typing) > doesn't seem to be yours. > > My point is something like bookmarks that are used so much > > By you. Not by everyone. (Says both our metrics data and anecdotal > experience.) > > It is very, very hard to design a UI that works for everyone's workflow. > Bookmarks are not a part of the normal workflow for a large fraction of > users. Tying login to them is not going to fly. > > With today's new touch UIs we should avoid different > > > functions for different mouse buttons! > > I admire your willingness to challenge pretty much every UI convention, but > normally working _with_ the OS and user expectations is a better move. > Right-click in Windows apps is here to stay. > > I would also float the idea of a normal > > > click opening the bookmark list, and a long click doing its current > > function of creating/editing a bookmark. > > No. > > It's obvious you really want to help make Chromium better, but I don't think > the ideas you're proposing are the best ways to do it. We're currently > working on both bookmark and form filling improvements. Perhaps after we > get those checked in, and maybe also when we have an extension system, it > will make sense to revisit some of these to see if any of your problems have > been addressed, or if your ideas would make sense as extensions. > > PK --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
