- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Tue, 29 Nov 2011 08:51:14 -0800
- To: www-style@w3.org
On 11/28/2011 10:21 AM, Edward O'Connor wrote: > > 2. In addition, there are some a11y implications that are out of scope > for CSS, such as: > > * tabbing should cycle through only elements in this subtree > * asking assistive technology to start reading the document should > cause it to start reading at the beginning of the element and not > the beginning of the document, and it should stop reading at the > end of the element This is a good point. This problem would be solved if instead of using positioning tricks, the spec defined the fullscreened element as occupying its own canvas. > 3. The rendering section of the Fullscreen API spec currently suggests > using a z-index of 2147483647. :( This seems like a pretty broken way of speccing something, imho. ~fantasai
Received on Tuesday, 29 November 2011 19:05:34 UTC