[Universal] NAMESPACE_ERR (14): the operation is not allowed by Namespaces in XML
See original GitHub issueWhen using it with Angular Universal I get the following error on the server:
ERROR { NAMESPACE_ERR: NAMESPACE_ERR (14): the operation is not allowed by Namespaces in XML
code: 14,
message: 'NAMESPACE_ERR (14): the operation is not allowed by Namespaces in XML',
name: 'NAMESPACE_ERR' }
Enclosing the <round-progress>
inside *ngIf="isPlatformBrowser"
doesn’t help at all.
This may be related: angular/material2#7866
Issue Analytics
- State:
- Created 6 years ago
- Reactions:4
- Comments:8 (1 by maintainers)
Top Results From Across the Web
xml namespace issues when building an xml file in nodejs ...
I get the following error. NamespaceError: The operation is not allowed by Namespaces in XML. [XMLNS] Qualified name includes a prefix but the ......
Read more >Namespaces in XML - W3C
URIs can contain characters not allowed in names, and so cannot be used directly as namespace prefixes. Therefore, the namespace prefix serves ...
Read more >DOMException - Web APIs | MDN
NamespaceError. The operation is not allowed by Namespaces in XML. (Legacy code value: 14 and legacy constant name: NAMESPACE_ERR ).
Read more >Using Namespaces with XMLports - Dynamics NAV
Learn that when using the XMLport to import or export an XML document, you can set up multiple namespaces on the XMLport to...
Read more >https://perso.limsi.fr/pointal/_media/python:pqrc:...
Objects, Names and Namespaces 2 ... Simple External Process Control 14 ... Can continue on next line if an expression or a string...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
AFAIK that only happens when setting the
xmlns
through a template. It’s most likely throwing because of this instance in particular.The attributes are optional for inlined
svg
so it should be fine to remove them.