<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi all,<div><br></div><div>As a pet project I’ve been pecking away at supporting the Gamepad API on Mac. You can follow along in <a href="https://bugs.webkit.org/show_bug.cgi?id=134076">https://bugs.webkit.org/show_bug.cgi?id=134076</a>.</div><div><br></div><div>The first glaring thing I noticed is how out of date the current code is. The Gamepad code currently in the tree has gone over 3 years without any real development.</div><div><div><br></div><div>In the meantime the working draft for the Gamepad API [1] is much different than what’s in our tree. Also at least 1 other engine (Mozilla) has shipped support matching the newer API.</div></div><div><br></div><div>I plan to completely break what’s currently in the tree in a non-backwards compatible way. Grep’ing the tree I conclude that this is okay because:</div><div><br></div><div>- Only EFL and GTK have Gamepad support code</div><div>- The code only supports in-process WebKit1</div><div>- GTK has it disabled</div><div>- EFL has it enabled, but has also committed to dropping WK1 support</div><div><br></div><div>If I am wrong and somebody has a compelling reason to keep supporting the version of the API that exists in the tree today, please contact me here or in the bugzilla. *SOON*.</div><div><br></div><div>Thanks!</div><div>~Brady</div><div><br></div><div>[1] - <a href="http://www.w3.org/TR/gamepad/">http://www.w3.org/TR/gamepad/</a></div><div><br></div></body></html>