<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Consider implementing UIEvent.sourceDevice"
href="https://bugs.webkit.org/show_bug.cgi?id=146848#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Consider implementing UIEvent.sourceDevice"
href="https://bugs.webkit.org/show_bug.cgi?id=146848">bug 146848</a>
from <span class="vcard"><a class="email" href="mailto:rbyers@chromium.org" title="Rick Byers <rbyers@chromium.org>"> <span class="fn">Rick Byers</span></a>
</span></b>
<pre>Yes, there has been some brainstorming in the community about how we might want to extend this over time. Some ideas here: <a href="https://docs.google.com/document/d/1WLadG2dn4vlCewOmUtUEoRsThiptC7Ox28CRmYUn8Uw/edit">https://docs.google.com/document/d/1WLadG2dn4vlCewOmUtUEoRsThiptC7Ox28CRmYUn8Uw/edit</a>#. But as you say, the details can get complex, so I figure it's best to iterate incrementally in a careful scenario-driven fashion rather than go nuts all at once.
My focus right now is to solve one particular long standing problem for devices with both a mouse and touchscreen (so not itself that interesting for WebKit). But no one wants to make one-off hacks just for that, so we're trying to establish a reasonable device info pattern for the future.</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>