- From: Bruno Racineux <bruno@hexanet.net>
- Date: Wed, 07 Jan 2015 15:57:01 -0800
- To: Bruno Racineux <bruno@hexanet.net>, Florian Rivoal <florian@rivoal.net>
- CC: James Craig <jcraig@apple.com>, Fred Esch <fesch@us.ibm.com>, www-style list <www-style@w3.org>
On 1/7/15 1:08 PM, "Bruno Racineux" <bruno@hexanet.net> wrote: >>On 1/7/15 3:16 AM, "Florian Rivoal" <florian@rivoal.net> wrote: >> >>> >>>>On 07 Jan 2015, at 11:53, Bruno Racineux <bruno@hexanet.net> wrote: >>>>Unless all platform align with this[1], focus remains inconsistent: >>>>[1] http://patrickhlauke.github.io/touch/tests/results/ >>> >>>Ah, right. Do you know if these inconsistencies result from spec >>>violations (which specs?), or from specs not being specific enough? >> > >Well the TouchEvents spec didn't really start as a full spec, and in term >of the mouse events sequence, it became the wild west, and there are no >standards yet. > >If all vendors could agree on what should fire and what order, that would >be progress. And given the lack of consistent :focus and inadequate :active states for that. What about: :tap-in and :tap-out And use both *:tap-in and *:focus-in for full cross compatibility. That was the missing piece for me in regards to mobile and touch when I coded my accessible navigation menu.
Received on Wednesday, 7 January 2015 23:57:29 UTC