angular-docs-cn/packages/core
Kristiyan Kostadinov f2360aab9d fix(ivy): incorrect namespace for root node created through ViewContainerRef (#31232)
Currently in Ivy whenever we encounter a new namespace, we set it in the global state so that all subsequent nodes are created under the same namespace. Next time a template is run the namespace will be reset back to HTML.

This breaks down if the last node that was rendered was under the SVG or MathML namespace and we create a component through `ViewContainerRef.create`, because the next template function hasn't run yet and it hasn't had the chance to update the namespace. The result is that the root node of the new component will retain the wrong namespace and may not end up rendering at all (e.g. if we're trying to show a `div` inside the SVG namespace). This issue has the potential to affect a lot of apps, because all components inserted through the router also go through `ViewContainerRef.create`.

PR Close #31232
2019-06-27 09:50:52 -07:00
..
schematics Revert "build: update to rules_nodejs 0.32.2 (#31019)" (#31267) 2019-06-25 14:36:00 -07:00
src fix(ivy): incorrect namespace for root node created through ViewContainerRef (#31232) 2019-06-27 09:50:52 -07:00
test fix(ivy): incorrect namespace for root node created through ViewContainerRef (#31232) 2019-06-27 09:50:52 -07:00
testing fix(core): temporarily remove @deprecated jsdoc tag for a TextBedStatic.get overload (#30714) 2019-06-14 10:40:42 -07:00
BUILD.bazel build: convert entry_point to label (#30627) 2019-06-11 00:03:11 +00:00
PACKAGE.md docs: add package doc files (#26047) 2018-10-05 15:42:14 -07:00
index.ts refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
package.json build: upgrade zone.js to 0.9.1 (#30260) 2019-05-10 14:25:56 -07:00
public_api.ts build: publish tree of files rather than FESMs (#18541) 2017-08-31 15:34:50 -07:00