Skip to content

fix(overlay): expand flexible origin type to allow SVG elements #19199

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

Merged
merged 1 commit into from
Apr 29, 2020

Conversation

crisbeto
Copy link
Member

The typing of the FlexibleConnectedPositionStrategyOrigin is scoped to HTMLElement which doesn't cover SVGElement, even though we support it. These changes update the type.

Note that this should be a safe change to the public API, because we're widening the type.

Fixes #36381.

The typing of the `FlexibleConnectedPositionStrategyOrigin` is scoped to `HTMLElement` which doesn't cover `SVGElement`, even though we support it. These changes update the type.

Note that this should be a safe change to the public API, because we're widening the type.

Fixes #36381.
@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release labels Apr 28, 2020
@crisbeto crisbeto requested a review from jelbourn as a code owner April 28, 2020 19:49
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Apr 28, 2020
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn added lgtm action: merge The PR is ready for merge by the caretaker labels Apr 28, 2020
@jelbourn jelbourn merged commit d321d45 into angular:master Apr 29, 2020
jelbourn pushed a commit that referenced this pull request Apr 29, 2020
The typing of the `FlexibleConnectedPositionStrategyOrigin` is scoped to `HTMLElement` which doesn't cover `SVGElement`, even though we support it. These changes update the type.

Note that this should be a safe change to the public API, because we're widening the type.

Fixes #36381.
@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 May 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants