Skip to content

How does the Owns property work? #671

Description

@lukewarlow

I notice that AccessKit includes the concept of a node owning another node, but this doesn't seem to be implemented anywhere?

I'm interested in what the design for this is envisaged to be? If I set Node A to own Node C, but Node B marks it C as a child, will AccessKit handle this "properly"?

I would assume accesskit could gracefully handle this such that ATs see Node C as a child of A NOT B? Is this desirable?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions