Go to newshutch.com. Click on "Test drive it now!" Click on "Newshutch Blog" feed. Move over to the right side over the "mark read" link (which appears only when you're over a story). Click on the link (careful to not wiggle the mouse). Note that the new article's "mark read" link is not yet displayed. Move the mouse slightly and note that it appears. This may be a regression -- I only tested with TOT. But I tried Firefox and it worked there. I suspect this is something about which mouse DOM events we deliver in this case.
(In reply to comment #0) > I suspect this is something about which mouse DOM events we > deliver in this case. I think this bug is about WebKit not sending mouse DOM events when the mouse is stationary and elements move under the mouse pointer. In your steps to reproduce, it is enough, for example, to press the Shift key to get the link to appear, because that probably does a hit-test, which results in hover states being updated.
In shipping Safari, the behavior is actually somewhat worse: you need to move the mouse more than slightly, to get out of the hidden "mark read" text. See also: bug 4117.
(In reply to comment #0) > This may be a regression -- I only tested with TOT. (In reply to comment #2) > In shipping Safari, the behavior is actually somewhat worse: you need to move > the mouse more than slightly, to get out of the hidden "mark read" text. So, not a regression.
(In reply to comment #1) > In your steps to > reproduce, it is enough, for example, to press the Shift key to get the link to > appear, because that probably does a hit-test, which results in hover states > being updated. The reason that hitting the shift key works in Safari is that Safari calls +[WebHTMLView _postFlagsChangedEvent:] when it sees an NSFlagsChanged event. Sadly we couldn't figure out a way to do this without some code in the application, so it won't work properly in other WebKit applications. We should probably revisit this at some point.
This site looks like it's about ready to shut down. See also: <http://newshutch.com/2007/04/16/newshutch-update-2/>
Closing as INVALID as the website is no longer available and there's no reduced test case.