Skip to content

Document control attributes for cdkTrapFocus #8082

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jelbourn opened this issue Oct 27, 2017 · 2 comments
Closed

Document control attributes for cdkTrapFocus #8082

jelbourn opened this issue Oct 27, 2017 · 2 comments
Labels
docs This issue is related to documentation help wanted The team would appreciate a PR from the community to address this issue P2 The issue is important to a large percentage of users, with a workaround

Comments

@jelbourn
Copy link
Member

Currently cdkFocusRegionStart, cdkFocusInitial, and cdkFocusRegionEnd (see #6960) are undocumented.

@jelbourn jelbourn added docs This issue is related to documentation help wanted The team would appreciate a PR from the community to address this issue P2 The issue is important to a large percentage of users, with a workaround labels Oct 27, 2017
amcdnl added a commit to amcdnl/material2 that referenced this issue Oct 30, 2017
mmalerba pushed a commit that referenced this issue Oct 30, 2017
* docs(focus): Add docs for regions #8082

* docs(a11y): add more desc for focus trap
@amcdnl amcdnl added the has pr label Nov 5, 2017
@willshowell
Copy link
Contributor

I think this can be closed

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
docs This issue is related to documentation help wanted The team would appreciate a PR from the community to address this issue P2 The issue is important to a large percentage of users, with a workaround
Projects
None yet
Development

No branches or pull requests

4 participants