On 09/14/15 21:53, Bruce Cran wrote: > On 9/14/15 1:39 PM, Laszlo Ersek wrote: > >> I never used the Issues pages (as anything other than a non-logged in >> lurker). But, if it resembles their code view etc pages, I think I'll be >> in trouble. Hotkeys in a browser... Brrr. It's just too heavy-weight for >> a browser. > > I can't say I'm much of a fan of Github's interface, and for us suspect > the Issues feature would be too simple. I don't see the problem with > hotkeys in a browser though - surely being able to press '/' to search, > 'esc' to close a dialog or '?' to get help is better than having to move > the mouse to click buttons?
Personally, I disagree. I like to use the "Search in Page" browser function, locate the (*aptly named*) link, hit ESC to exit the search, then hit Enter to follow the link (or open it in a new windows with Middle-Click or the key combos that do the same from the local menu). Websites shouldn't be sold as interactive desktop apps, beacuse they aren't. All those attempts trying to claim otherwise have without exception failed for me. For some extreme offenders, I even have GreaseMonkey scripts that disable this key-grabbing mis-feature. The "Search in Page" browser function is supposed to work identically on all websites. Pressing "/" on GitHub (possibly inadvertently) triggers their own search function, while on another key-grabbing website it might cause daemons to fly out of one's nose. Stop that madness already. I know my desktop apps' key combos because there are only a handful of them, and I use them all day. I don't know every random website's combos because there are uncountably many of them. ... As I said, personal opinion :) Thanks Laszlo _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
