upvote

points

by hirako200013 hours ago |
comments
upvoteby Terr_6 hours ago|
next
[-]
> But they insisted. E.g hijack brosser native controls.

[Rant-Example] The goshdarn ticketing-system hijacks alt-f, so that instead of opening the File menu of my browser, and instead toggles the favorite-status of whatever ticket I happen to be viewing.

reply
upvoteby twic31 minutes ago|
parent|
next
[-]
A mistake was made early on even letting web apps see keystrokes like that. In a better world, modifier keys were used in a principled way from the start - only the window manager gets to see meta-anything, only the shell or GUI app gets to see control-anything, and web apps can work with alt-anything.
reply
upvoteby walletdrainer3 hours ago|
parent|
prev|
[-]
Have you tried creating a ticket complaining about this?
reply
upvoteby cineticdaffodil1 hours ago|
parent|
[-]
Press alt f to pay respect with the "respect my AI.thority" subscription
reply
upvoteby themanualstates7 hours ago|
prev|
[-]
To be fair, the native browser controls have had too many quirks and features fox UX/UI consistency.

Corporate needs their Brand™ look precisely as specified in their expensive Style Guide. IBM wouldn't want the Google vibes of Android Material Design TextFields, I imagine.

Scratch beneath the visuals, and starker technical differences appear.

Safari on iOS (used to?) has a 350ms debounce delay on every tap / click, in case you want to do a multitouch gesture.

JavaScript (Frameworks) were the only way this arbitrary delay to user input could be reduced before 2015, when Apple finally released a native API for this.

https://webkit.org/blog/5610/more-responsive-tapping-on-ios/

reply
upvoteby eru5 hours ago|
parent|
[-]
> To be fair, the native browser controls have had too many quirks and features fox UX/UI consistency.

Well, too many to have a single website be consistent across browsers.

But as a user I'm using one specific browsers, and I expect all websites be consistent for that browser.

reply