What has been marked can never be unmarked
-
...or at least that's how it appears on a touch screen.
On desktop, marking and then unmarking a topic in /unread goes:
-> mouseenter -> click -> click -> mouseleave
It's a little weird that the second click turns the checkmark blue, but you have some prior warning that a blue checkmark means "selectable" rather than "selected", and it soon goes away when you move the mouse.On a touchscreen:
-> tap -> tap
and it looks like the topic is still marked, but it's changed colour because , who knows what that's supposed to mean, and the blue checkmark abruptly disappears if you tap on a different topic.The touch interface I would expect is:
-> tap -> tapAnd no, I have no idea how to implement that for touch devices but retain the UI hint on hover. Them's the breaks.
-
@clatter said in What has been marked can never be unmarked:
I have no idea how to implement that for touch devices but retain the UI hint on hover
Why should the on-tap behavior be circumscribed by the on-hover behavior?
-
The icon is being set and reset via dedicated event handlers instead of through CSS
:hover
?
-
@Zecc said in What has been marked can never be unmarked:
The icon is being set and reset via dedicated event handlers instead of through CSS
:hover
?i assume the blue check is a :hover CSS, that would be why it persists when using tap to unselect, the virtual mouse is where you last tapped to :hover applies.
-
@accalia Actually, it's a Bootstrap Tooltip (which requires JS), CSS'd to buggery to look like a hover thingy.
Before hover:
During hover:
-
@accalia said in What has been marked can never be unmarked:
i assume the blue check is a :hover CSS
Yes, it seems to be a rule on
.category>ul>li .avatar .select:hover .fa-check
.I was not seeing it change when I manually set :hover on its parent div, that's why I thought they were .
The event handlers must be the tooltip, as @RaceProUK said.
-
@clatter said in What has been marked can never be unmarked:
Seems to work like that already on Edge.
-
@clatter I'm a bit confused about the links in those chains. Particularly, why some of them end at , but all of them begin there.
-
@anotherusername That's the bug exactly. It doesn't change back, when it should.
-
@accalia said in What has been marked can never be unmarked:
the virtual mouse is where you last tapped to :hover applies.
Why is this relevant for touchscreens....?
IMO the mouse should be independent from taps.
Holding the mouse down, and dragging with a separate finger should be the same as a pinch gesture.
-
@Yamikuronue ...oh.
I guess my confusion was in parsing as the author's own avatar instead of as the avatar of whichever user started the thread.
-
@xaade said in What has been marked can never be unmarked:
Why is this relevant for touchscreens....?
because that's how touchscreens work, it's also how applications know where it was that you picked your finger up from a drag action.
should it be relevant? I'm an engineer not a UX expert, Jim!
-
@accalia said in What has been marked can never be unmarked:
I'm an engineer not a UX expert, Jim!