Skip to content
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

Add documentation for overlay #396

Closed
aminebizid opened this issue May 5, 2016 · 3 comments
Closed

Add documentation for overlay #396

aminebizid opened this issue May 5, 2016 · 3 comments

Comments

@aminebizid
Copy link

aminebizid commented May 5, 2016

Is there any doc/example/tutorial showing how to use overlays, portal hosts and positioning strategies?

@devversion
Copy link
Member

I think, documentation for the overlay service will possibly come after #113 is completed.

@kara kara changed the title Overlay Add documentation for overlay May 6, 2016
@jelbourn
Copy link
Member

jelbourn commented May 9, 2016

Yep, documentation will come when the overlay is mature enough for use outside of our own components.

@jelbourn jelbourn closed this as completed May 9, 2016
andrewseguin pushed a commit to andrewseguin/components that referenced this issue Oct 15, 2018
* Currently if someone visits a link that contains a fragment that refers to an anchor element, the element won't be scrolled into view properly. This is because the `focusOnNavigation` calls `focus()` after the scroll into view. This causes the focused element to be visible in view.
* Removes an unnecessary workaround for fixing fragment URLs.

Fixes angular#396
@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 4, 2019
alexeagle pushed a commit to alexeagle/material2 that referenced this issue Nov 6, 2024
* Currently if someone visits a link that contains a fragment that refers to an anchor element, the element won't be scrolled into view properly. This is because the `focusOnNavigation` calls `focus()` after the scroll into view. This causes the focused element to be visible in view.
* Removes an unnecessary workaround for fixing fragment URLs.

Fixes angular#396
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants