Hi.
HTML5 introduces inert subtrees [1] which are supposed to make a
portion of the document inactive (not interactive for the user):
"When a node or one of its ancestors is inert, then the user agent
must act as if the element was absent for the purposes of targeting
user interaction events, may
On 09/27/2013 06:03 PM, Alexander Surkov wrote:
> Hi.
Hi,
>
> HTML5 introduces inert subtrees [1] which are supposed to make a
> portion of the document inactive (not interactive for the user):
>
> "When a node or one of its ancestors is inert, then the user agent
> must act as if the element was
Hi. Possibly they word it this way to have some room for use cases
other than dialog element. Also AFAIK inert subtree don't have
implementations yet so the wording is not really final. In either case
I agree the spec sounds a bit controversial stating that no user
interaction events but same time
Hey Alex, all.
On 09/27/2013 12:03 PM, Alexander Surkov wrote:
> Hi.
>
> HTML5 introduces inert subtrees [1] which are supposed to make a
> portion of the document inactive (not interactive for the user):
>
> "When a node or one of its ancestors is inert, then the user agent
> must act as if the
On Fri, Sep 27, 2013 at 01:27:19PM -0400, Joanmarie Diggs wrote:
> As a related aside:
> >
> > aria-hidden implementation varies from browser to browser: Chrome
> > removes it from accessible tree,
>
> Which I think makes a heck of a lot of sense. If for all intents and
> purposes it is not there
Hi, Joanie.
A primary use case I can think of is a dialog. When it appears on the
screen then everything but dialog content turns into inert subtree. So
basically it's grayed-out content but still visible for the user. I
don't have other use cases, probably Steve Faulkner knows something.
So basi
On 09/27/2013 01:54 PM, Alexander Surkov wrote:
> A primary use case I can think of is a dialog. When it appears on the
> screen then everything but dialog content turns into inert subtree. So
> basically it's grayed-out content but still visible for the user. I
> don't have other use cases, proba
Yep, STATE_ACTIVE as you describe it might do a trick. Basically if AT
are ok that STATE_INACTIVE window contains STATE_ACTIVE dialog then it
should be working.
Alex.
On Fri, Sep 27, 2013 at 2:45 PM, Joanmarie Diggs wrote:
> On 09/27/2013 01:54 PM, Alexander Surkov wrote:
>
>> A primary use case
