- From: White, Jason J <jjwhite@ets.org>
- Date: Thu, 10 Sep 2015 18:09:56 +0000
- To: "lwatson@paciellogroup.com" <lwatson@paciellogroup.com>
- CC: Michiel Bijl <michiel@agosto.nl>, Richard Schwerdtfeger <schwer@us.ibm.com>, Bo J Campbell <bcampbell@us.ibm.com>, Fred Esch <fesch@us.ibm.com>, PF <public-pfwg@w3.org>
> On Sep 10, 2015, at 13:42, Léonie Watson <lwatson@paciellogroup.com> wrote: > > Firefox does seem to be trying to handle the conflict though. After some more quick tests, it seems that the DOM remains unchanged but that the tab order changes based on the flex/visual order. Does it behave correctly, i.e., use the DOM tree order, if tabindex=0 is specified on elements? More generally, I think we should continue to explore the idea of developing CSS properties for defining the navigation sequence. ________________________________ This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. ________________________________
Received on Thursday, 10 September 2015 18:10:27 UTC