feat(DomRenderer): Adding support for document fragments in SVG foreign objects#9458
Conversation
|
Could you please create an issue on https://github.com/angular/angular.io for this to be documented, linking this PR ? Code LGTM, I'll merge once the issue on angular.io is created. Thanks. |
| inject( | ||
| [TestComponentBuilder, AsyncTestCompleter], | ||
| (tcb: TestComponentBuilder, async: AsyncTestCompleter) => { | ||
| tcb.overrideView( |
There was a problem hiding this comment.
minor: switch to tcb.overrideTemplate(html)
|
I've added the issue #6190 in the PR description |
|
@vicb Using |
Yep, no problem |
|
Please create an issue on angular.io as requested above |
|
Thanks ! |
|
You are very welcome Sir! :-) Rock on! |
This is a Dart rewrite of Angular2 PR: angular/angular#9458 Detected while migrated svg component from AngularDart to Angular2 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=130939492
This is a Dart rewrite of Angular2 PR: angular/angular#9458 Detected while migrated svg component from AngularDart to Angular2 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=130939492
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behavior? (You can also link to an open issue here)
This PR solves the issue described by: #6190
Document fragments within SVG foreign objects can't be created since the renderer continues to use SVG namespace for contained elements.
This does currently not work because the renderer would try to render the content of the
foreignObjectelement using the SVG namespace.What is the new behavior?
By added the xhtml namespace explicitly to
NAMESPACE_URISone can now write a document fragment within aforeignObjectelement by defining the namespace prefix:Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:
…gn objects