No mouseover

I usually am. Both my employer’s laptop and my windows laptop have touch screens. I only get mouseover on my Mac.

I miss it. :cry:

My laptop has a touchsceen, but most commonly I’m using it docked with a second monitor and mouse. But the mouseover doesn’t work because the site detects that I have a touchsceen.

Ideally, the site would turn mouseover on/off based on the presence of a pointing device. I don’t think that’s possible in browsers (yet), so maybe the mouseover could be on for everyone? Is there any problem with having it enabled for touch devices?

There was quite a lot of discussion about touchscreens and mouseover in this thread.

I asked my husband, a web developer, about wherever there was anything inherent about having a touchscreen that made it hard to implement mouseover.

He said there isn’t. But he says a common problem is that the code assumes you have mouseover and relies on it for some functionally, but the mouseover doesn’t work (despite being implemented) because you don’t have a separate pointing device.

He thinks the issue must be in the package of utilities Discourse is using, which is trying to protect developers who use it from making that kind of mistake.

Yes, Surface Pro. If I turn off touch while I open SDMB, mouseover works. But that is a pain to remember to do every time. (needs me to run a small script)

As far as I can see, to prevent accidental and annoying not-wanted mouseovers, Discourse uses touch capability to differentiate smartphones/tablets (keyboard and mouse -less devices) from Mac/PC. OK a while ago but in the last several years a lot of PCs have acquired touch, keyboard and mouse. Needs a better way to do this if still needed. Even a manual choice would be better.

One suggestion would be to detect all touch events and only disable mouseover events when one is currently active.

Another simpler idea might be to never completely disable if the UserAgent is a desktop browser. Most mouse users would use one of those.

I’m using a laptop that does not have touchscreen and never has. Mouseover is intermittent at best for me.

raking up the rake-up :grinning:

Is there any intention to look at this issue?

As stated upstream, it’s a limitation of the browser tooling. There’s literally nothing we can do about it, because we can’t detect this state – “system has both a mouse and a touchscreen”. This may change in the future as browsers improve, however.

Is there a need to disable mouseover for touch screens? What’s the downside of it being always on?

I believe it turns everything into a double-tap on touch. One tap to reveal the “hover”, then a tap to activate. That’s what I remember. So yeah, pretty traumatic.

How about

  1. disable mouseover in mobile / enable it in desktop mode
    or
  2. make it a setting

Or, if you REALLY don’t want to do either of those, how about
3) just give up entirely on mouseover?

It’s problematic to have it sometimes work and sometimes not work in ways that are confusing to the user. And I was just looking at a thread where apparently some mod made a moderation decision in part based on what the mouseover showed – which isn’t a uniform experience.

Yes, I’m feeling bitchy about this, because most of my browsing is in Win10 these days, and like all good Win10 devices, my laptops have touchscreens. And I’m finding the whole thing very frustrating.

My preference would be (2), as I really like mouseover, and miss it.

I could probably live with double-tapping on my phone. I really do miss mouseover. :cry:

Just reinforcing this request and also wondering (as others have) if it could switch depending on whether you’re serving up the mobile website or the desktop version.

There’s a draft specification for Media Queries Level 4 originally published in 2014 that I think provides better support. It’s still draft, but every major browser (except IE) already implements it.

In particular, the any-hover:hover feature will indicate if the device has any hover-capable input.

If I disable touch, start a browser, then reenable touch, mouseover works in some themes.
So how about removing this out-of-date way to detect smartphones and just create some smartphone themes?

Raking up the last rake up.
Seems this gets discussed, with potentially useful suggestions, but no definitive answer on when/if it will be worked on or fixed. Note as per other posts, I am aware this is Discourse related

Is this really dead for touch-screen PC users? Or in the pipeline somewhere?

It depends if browser manufacturers give developers the ability to distinguish between touchscreen with keyboard, and touchscreen only. Right now that’s not possible. Best to follow up with the browser companies and ask.

You can read more about it here.

Also ask yourself: what if the user with the touchscreen computer unplugs their mouse? What happens then?

My laptops with touch screens also have a built in touchpad that can’t be unplugged. I almost never use a mouse. I also miss the “mouse over”.

Mouseover has been intermittent at best since the board software switch. I’ve been using the same laptop the whole time, that does not have touchscreen and never has.