[Webkit-unassigned] [Bug 101857] Updating mouse cursor on style changes without emitting fake mousemove event

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Dec 3 02:42:08 PST 2012


https://bugs.webkit.org/show_bug.cgi?id=101857





--- Comment #51 from Aivo Paas <aivopaas at gmail.com>  2012-12-03 02:44:31 PST ---
(From update of attachment 177187)
View in context: https://bugs.webkit.org/attachment.cgi?id=177187&action=review

>>> Source/WebCore/dom/Document.cpp:-5755
>>> -
>> 
>> I don't think it is a good idea to change this behaviour in this patch. We should figure out why it was introduced in the first place and fix it in another bug if we think it is still a good idea.
> 
> I also thought about making the behavior change separate. Skipping the hovered() check should be enough to go without the change. I'll also dig up where the condition was introduced to see if there's a good reason for not being consistent with other browsers.

Found where this behavior was introduced: http://trac.webkit.org/changeset/9957

Quoting from the Changelog:
> (b) If you mouse down on a non-selectable region and start moving, then the behavior has changed.  Instead of not updating at all, we mark the chain at the time the mouse goes down, and we restrict :hover/:active updates to only apply to elements that are in that chain.  This yields perfect hover/active control behavior, even when :active has been applied hierarchically.

Not sure what the "perfect hover/active control behavior" meant 7 years ago but it clearly is not what other browsers think about it today. CSS spec does not mention such limiting condition for applying :hover pseudo class.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the webkit-unassigned mailing list