On Fri, 08 Jun 2012 05:05:11 +0200, Mark Callow callow_m...@hicorp.co.jp
wrote:
On 08/06/2012 06:09, Ian Hickson wrote:
The dire warning doesn't work. I'm just saying that's the direction that
operating system vendors have been going in; that disallowing it in the
browser case is not a
On 6/19/12 1:56 PM, Charlie Reis wrote:
That's from the [if] the user agent
determines that the two browsing contexts are related enough that it is
ok if they reach each other part, which is quite vague.
This is, imo, the part that says unrelated browsing contexts should not
be able to reach
On Tue, Jun 19, 2012 at 11:38 AM, Boris Zbarsky bzbar...@mit.edu wrote:
On 6/19/12 1:56 PM, Charlie Reis wrote:
That's from the [if] the user agent
determines that the two browsing contexts are related enough that it is
ok if they reach each other part, which is quite vague.
This is, imo,
On Tue, 19 Jun 2012, Charlie Reis wrote:
On Tue, Jun 19, 2012 at 11:38 AM, Boris Zbarsky bzbar...@mit.edu wrote:
On 6/19/12 1:56 PM, Charlie Reis wrote:
That's from the [if] the user agent
determines that the two browsing contexts are related enough that
it is
On Tue, Jun 19, 2012 at 2:16 PM, James Graham jgra...@opera.com wrote:
The way the process here works is that Hixie reads these emails agrees that
the change is a good idea (hopefully; in this case it seems likely since we
seem to have three implementors in agreement) and it happens. There
Hi all,
I recently experimented with keyboard accessibility of media elements.
I found that browsers don't provide a default tabfocus on media
elements nor do they provide keyboard interactivity. I had to put
explicit @tabindex attributes onto the media elements to allow them to
at least receive
IE has lead the way. Thanks for your contributions to the Chrome/WebKit process.
I've setup a webapps-UI CG at the W3C to help track these efforts.
I suspect we'll see more traffic from authors as web components grow out of
their development/experimental status in WebKit.
On Jun 19, 2012, at
On Wed, 20 Jun 2012 05:43:20 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
Hi all,
I recently experimented with keyboard accessibility of media elements.
I found that browsers don't provide a default tabfocus on media
elements nor do they provide keyboard interactivity. I had to
On Wed, Jun 20, 2012 at 2:51 PM, Simon Pieters sim...@opera.com wrote:
On Wed, 20 Jun 2012 05:43:20 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
Hi all,
I recently experimented with keyboard accessibility of media elements.
I found that browsers don't provide a default tabfocus
