- From: Bart Nagel via GitHub <sysbot+gh@w3.org>
- Date: Sun, 03 Apr 2016 04:42:19 +0000
- To: public-touchevents@w3.org
Maybe there's something important I'm missing here about the process, but isn't that attitude causing a bit of a catch-22? If it's not added to the recommendation or specification, what incentive to the browsers have to implement it? It seems to me the first step would be to just go ahead and add it, unless there's a solid reason why not. "Browsers are reluctant to adapt" doesn't seem surprising if it's not there in the specification they're trying to adhere to. Or is there some other reason the browsers are against implementing this? -- GitHub Notification of comment by tremby Please view or discuss this issue at https://github.com/w3c/touch-events/issues/62#issuecomment-204867670 using your GitHub account
Received on Sunday, 3 April 2016 04:42:28 UTC