<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - :hover is sticky on iOS, even on touch-friendly webpages"
href="https://bugs.webkit.org/show_bug.cgi?id=158517#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - :hover is sticky on iOS, even on touch-friendly webpages"
href="https://bugs.webkit.org/show_bug.cgi?id=158517">bug 158517</a>
from <span class="vcard"><a class="email" href="mailto:benjamin@webkit.org" title="Benjamin Poulain <benjamin@webkit.org>"> <span class="fn">Benjamin Poulain</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=158517#c2">comment #2</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=158517#c1">comment #1</a>)
> > I don't think we can easily fix :hover because of legacy content.
>
> I don't understand why you're citing legacy content as a reason, when the
> suggestion
> is specifically to *not* change the semantics for legacy content.
> Only non-legacy content would be affected.</span >
We could certainly have the behavior of :hover change depending on the viewport meta tag or other signals that a page is mobile friendly. I generally try to avoid "modes of operations" like that and prefer to have a consistent behavior.
I was not rejecting your idea of getting rid of :hover for mobile. Just giving my opinion on how I would prefer the use case to be handled.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>