W3C Charters Pointer Events Working Group
Following Microsoft’s submission of the Pointer Events specification, the W3C announced Friday the launch of the Pointer Events Working Group. The group intends to use Microsoft's proposal, based on the APIs available today in IE10 on Windows 8, as the starting point for a Recommendation track specification, an important step towards interoperable support on the Web. In their announcement, the W3C said, “enabling content creators to use a single [pointer] model for different input types will make content creation more efficient and inclusive.”
Last week during the W3C’s annual Technical Plenary and Advisory Council (TPAC) meeting in Lyon, France, members of the W3C met informally to discuss Pointer Events. Present in the meeting were representatives of Google, Mozilla, Opera, Nokia, LG, Intel, Microsoft, and others. With the overwhelming support pointer events received from browser vendors and Web developers, consumers and developers benefit. We look forward to working together to bring the next generation of input to the interoperable Web through standards.
Jacob Rossi
Program Manager
Comments
Anonymous
November 12, 2012
The comment has been removedAnonymous
November 12, 2012
Really although he has heard that the release preview version which IE10 for Windows 7 will come out tomorrow? www.liveside.net/.../internet-explorer-10-for-windows-7-preview-coming-tomorrowAnonymous
November 12, 2012
Hey all, can anyone confirm: among the Windows 8 tablets (windows.microsoft.com/.../all-pcs), which one is this: ads1.msn.com/.../skydrive-hero.jpg ? It looks slightly like "Lenovo Thinkpad Tablet 2", but its pretty sleek. Can anyone please tell if its a future model or the existing one? :) @IE-team, thanks alot for the heads up. Microsoft's touch model is great. I'm not surprised. Because Microsoft is always propose state-of-the-art solutions to W3C and C++ ISO... a deserving software giant. (at least better than most of the wannabes out there.. no offence!) 8-)Anonymous
November 12, 2012
Real McCoy, I agree with you entirely. It's abysmal really. Of the 43 bugs I've submitted, the breakdown is as follows: Won't fix - 16 By Design - 6 Fixed - 12 Active - 3 Not Reproducable - 6 The numbers speak for themselves. The only strategy is to just keep reopening the unfixed bugs they closed. Maybe then they'll get the memo.Anonymous
November 12, 2012
The comment has been removedAnonymous
November 13, 2012
@Mike Dimmick, how about you take a look at this issue: connect.microsoft.com/.../support-dom-level-3-xpath Now try the test-case mentioned in the description (www.freewebs.com/.../205-dom-level-3-xpath.html) on IE10 release preview in Windows 7 and IE10 RTM on Windows 8 (both latest versions till date). Clicking on document.implementation.hasFeature('xpath', '3.0') button would return "false" Try it on Firefox, it would return "true". Now, read the last comment by Microsoft. Do you honestly think they made a "mistake" OR they deliberately lied? In my previous post, I mentioned another bug-report which was "mistakenly?" closed as Fixed and they "mistakenly?" replied that "This issue was resolved in Internet Explorer 10 released on 10/26/2012." Either very incompetent people are managing bug-reports (copy/pasting text) or they are just staging a drama "we are actually listening to you!" The Visual Studio team OTOH, carefully read the bug report and carefully reply to the people. Every reply varies from one another. No copy/paste and no time-waste. Honesty! just honesty! is it too much to ask from IE team?Anonymous
November 13, 2012
The comment has been removedAnonymous
November 17, 2012
Great Thank you for sharing excellent information. Your website is so cool. I am impressed by the details that you’ve on this web site. It reveals how nicely you understand this subject. Bookmarked this web page, will come back for extra articles. You, my pal, ROCK! I found just the info I already searched everywhere and just could not come across. What a perfect web site. http://ammumarket.netAnonymous
November 21, 2012
@Joe B. Interestingly, my results are completely different to yours (I have made a jsfiddle with your function and an additional corrected function that actually changes .top and .left as I assume you meant: http://jsfiddle.net/xUtcZ/1/). IE10: Test 1: 597ms Test 2: 2430ms FF17: Test 1: 1025ms Test 2: 4403msAnonymous
November 21, 2012
Okay - blame the awful comment section for this going under the wrong article.
