Search Ideas
780 ideas match your query.:
Add hover effects to schemed buttons so there’s consistency with the existing hover effects for links.
I tried removing hover effects on links in dev and the user experience suffered as a result.
Especially for smaller links, like the hash links in idea headers, it’s nice getting that visual feedback that you are in fact hovering over the link and your click won’t miss it.
Edwin says to either have hover effects for all clickable items or none of them. Buttons currently don’t have hover effects but links do.
I could remove hover effects from links. macOS links in System Settings don’t have a hover effect either. (They don’t even have a pointer cursor but IMO that’s going too far.)
Edwin says to be consistent. Either have hover effects for all clickable items or none of them.
I could remove hover effects from links. macOS links in System Settings don’t have a hover effect either. (They don’t even have a pointer cursor but IMO that’s going too far.)
I went back and forth on this. Native macOS buttons don’t have a hover effect and the human-interface guys at Apple are world class. I’m inclined to defer to their expertise. They know things I don’t.
@edwin-de-wit says buttons should have a hover effect.
Having implemented this, a problem has surfaced: when linking to an old version of an idea, the alert “You’re about to comment on an old version of this idea. Are you sure …” shows. That’s jarring if you didn’t want to comment but merely look at the idea.
As of acb14e3, the revision button is an icon button that lives next to the collapse icon button.
Therefore, the button doesn’t need to be hidden anymore.
It could go both ways. Someone may have already read an idea and just wants to revise it, in which case having to scroll to the bottom is cumbersome.
That would mean the revise button would be at the top of the idea. But presumably, people would typically want to revise an idea after they finish reading it. Meaning after they reach the bottom.
I could turn the ‘Revise…’ button into an icon button that lives next to the collapse icon button. It could just have a pencil for an icon.
That way, the button wouldn’t need to be hidden anymore.
Should I be showing the comment form by default on ideas#show?
To avoid scrolling past content, I could remove the autofocus on the textarea unless a certain query parameter is given.
The ‘Revise…’ button is hidden when the comment form is open. It makes sense to hide it because it doesn’t belong in that context. But once hidden, the user has no quick way to revise an idea. Maybe the first thing they want to do after opening ideas#show is not comment but revise.
Then the autofocus on the textarea would force a scroll basically to the bottom of the page. For sufficiently long ideas, that means scrolling past content the user wants to see.
Should I be showing the comment form by default on ideas#show?
Could probably use Turbo frames instead.
That would probably be stretching the capabilities of Stimulus…
There could be a separate button to filter comments down.
The red ‘Criticized’ label could be clickable and filter the displayed comments ‘in place’.
The red ‘Criticized’ label could be a link leading to a filtered version of ideas#show.
The red ‘Criticized’ label could be clickable and lead to a filtered version of ideas#show.
The red ‘Criticized’ label shows how many outstanding criticisms an idea has. For example ‘Criticized (5)’ means the idea has five outstanding criticisms.
But if there are lots of comments, including non-criticisms and addressed criticisms, it’s hard to identify outstanding criticisms.
There should be an easy way to filter comments of a given idea down to only outstanding criticisms.