[Angular Universal] mat-datepicker-toggle at SVGSVGElement.setAttribute - the operation is not allowed by Namespaces in XML\nNAMESPACE_ERR
See original GitHub issueBug, feature request, or proposal:
Bug
What is the expected behavior?
Calendar renders server side
What is the current behavior?
using
<mat-form-field>
<input matInput [matDatepicker]="picker" placeholder="Date">
<mat-datepicker-toggle matSuffix [for]="picker"></mat-datepicker-toggle>
<mat-datepicker #picker></mat-datepicker>
</mat-form-field>
throws
Uncaught (in promise): NAMESPACE_ERR: NAMESPACE_ERR (14): the operation is not allowed by Namespaces in XML\nNAMESPACE_ERR: NAMESPACE_ERR (14): the operation is not allowed by Namespaces in XML\n at Object.exports.NamespaceError (/Users/Patrick/Repos/myapft/node_modules/domino/lib/utils.js:28:45)\n at SVGSVGElement.setAttribute
What are the steps to reproduce?
Use the above snippet in any universal applications
What is the use-case or motivation for changing an existing behavior?
to support server side rendering
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
β@angular/animationsβ: β5.0.0-rc.2β, β@angular/cdkβ: β^2.0.0-beta.12β, β@angular/commonβ: β5.0.0-rc.2β, β@angular/compilerβ: β5.0.0-rc.2β, β@angular/compiler-cliβ: β5.0.0-rc.2β, β@angular/coreβ: β5.0.0-rc.2β, β@angular/flex-layoutβ: β2.0.0-rc.1β, β@angular/formsβ: β5.0.0-rc.2β, β@angular/httpβ: β5.0.0-rc.2β, β@angular/materialβ: β^2.0.0-beta.12β, β@angular/platform-browserβ: β5.0.0-rc.2β, β@angular/platform-browser-dynamicβ: β5.0.0-rc.2β, β@angular/platform-serverβ: β5.0.0-rc.2β, β@angular/routerβ: β5.0.0-rc.2β, β@angular/service-workerβ: β5.0.0-rc.2β,
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (2 by maintainers)
Top GitHub Comments
@hamedbaatour looks like it hasnβt been merged in yet
https://github.com/angular/material2/pull/7882
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.