Middle-click scroll (called Autoscroll) is a WebKit feature and is supported in the latest builds, although there are some bugs open against it, so it may not work entirely as expected.
- Itai On May 3, 7:50 am, "Josh @ Dreamland" <[email protected]> wrote: > Two things I'm not sure the browser supports. > I don't see a way to have the middle button scroll when you click > outside a link with it, and the password manager will give me any > password it has stored without prompting for a master password, which > is alarming. > > I'm confident Google has taken precautions to make sure you can't just > steal password data from a website, but I think I'd feel more > comfortable if they were encrypted with the hash of a master password, > either prompted for at startup, or at your option, stored somewhere > that not just everybody can find it. I'm thinking of shared computers. > It's one thing for someone to be able to log in as you from your own > computer, but another for them to get the general idea behind all your > passwords by, well, having a list of them all. PayPal comes to mind; > wouldn't be happy for that to be plainly visible from options. Storing > only the hash of master password and prompting for the original before > decrypting and showing the rest of the passwords would be nice, and > not that hard to implement. (I'm almost volunteering, but right now > I'm hoping to God they have a set of functions that just link > differently on Linux and Mac that will be able to call a message box > and a string prompt. Please Google, please have done that. That'd make > this whole open source thing make SENSE.) > > I think in the perfect world, passwords would be hashed client side > and then sent to the server as unrecognizable crap, but if Google is > storing raw password data, I guess that's not the case. > > Anyway, mouse wheel. That could either be really difficult to > implement or really easy, depending on if the code is basically > for (int i=0;i<link_count;i++) if (in_bounds(mouse.x,mouse.y)) > linkid=i; > if (linkid) > { > ... > > } > > In which case, I could just add an else {} which sets an additional > byte in their global structure I've been hearing about, and if that > byte or a bit in that byte is true, enable scrolling. (I'd also have > to store two shorts for X and Y positioning of original click, but > meh). > > Figured I'd ask if those were already in and I missed them, or if > they're planned, before I start digging. Which will likely have a > large learning curve in itself. > > Thanks. --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
