[Webkit-unassigned] [Bug 46733] REGRESSION (r67261): Middle-mouse-release opens links regardless of "press" location

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Sep 30 00:18:59 PDT 2010


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


Brenton <webkit at appsforartists.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |webkit at appsforartists.com




--- Comment #12 from Brenton <webkit at appsforartists.com>  2010-09-30 00:18:59 PST ---
This is a regression.  Whatever you guys had before worked awesome (except, apparently, for the @onclick bug that r67261 resolved).

Allowing DOM events to trigger native handlers would make the Web an even more powerful platform, as it would allow JavaScript authors to have finer control over the page.  With both Chrome and Safari now supporting extensions, as well as the innovations going on in input devices, I'm sure there are use cases where someone could build something really cool by dispatching phantom MouseEvents.  That said, I really don't see the point in contesting this.  If you guys want to mimic Firefox's separation of DOM and native handling, I won't complain.

I would, however, like middle-mouse events to have the same level of control as left-mouse events.  Specifically, just as preventDefault() can interrupt the native handler for an onLeftClick, it should be able to block the native handling of an onMiddleClick.

It's easier make accurate predictions and expectations of the browser when there are fewer special cases (for instance, when the middle-click API behaves just like the left-click API).  Also, extension authors often provide custom functionality in response to middle-clicks, and mouseEvent.preventDefault() is an important tool to that end.

If I misunderstood your remarks about preventDefault, I apologize.  


This sounds like it's more than just a quick fix.  Any chance that the r67261 patch can be rolled-back and reapplied when it includes a fix for this issue?  I use an extension that is bound to middle-click.  The constant spawning of links I didn't click is getting annoying.

Thanks as always for your constant work to improve the Web.

-- 
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