More Native UI/UX (including simple refinements like not having the pointer cursor used on buttons/items)
Feature function
I have something that’s just bothersome that I hope is quick to refine… something that’s effectively looking/acting as a native app should act like one rather than having a website-like UI/UX. For example, the buttons, left navigation items, individual items in lists & details, etc. that are clickable have the pointer cursor be used when a native app would have it still be the default cursor.
This is something that should be doable (seems adding cursor:default; to html, body [main text areas], a [left navigation], and .btn:hover:not([disabled]) [buttons at the bottom of the window] takes care of major items, but I’d imagine there’s more to it than those few items.)
Again, that’s how natives apps do it and it it would make sense to follow that convention as the app sees further attention.
Meanwhile having focus states, reasonable hover/active states, etc. for interactive items to help illustrate they’re interactive as needed rather than relying on the pointer cursor. (don’t want to abandon important UI/UX/accessibility principals… just want to make it more like a native app since it’s aiming to look like one to some degree rather than appearing like its own thing.)
Slack & Discord have the pointer cursor where it’s not troublesome, but the fact they totally make it appear like their own thing rather than looking anything like what might be a native app helps that… the BitWarden app is currently somewhere in an odd middle ground & should choose a direction… I see it being more native than being a fully unique UI/UX which then has it where things like the pointer cursor going away to follow that convention (among others that help make it look & act more like a native app).
This could potentially apply to the browser extension’s window as well.