You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Angular 15 + jsonforms 3.1.0
When a page with form is opened error appears in chrome console.
Reproduced only if showUnfocusedDescription: true and for fields with type: number | integer.
In Chrome, Edge: ERROR DOMException: Failed to execute 'setAttribute' on 'Element': '||' is not a valid attribute name.
In Firefox: ERROR DOMException: String contains an invalid character
The template had a bug closing the ngIf that checks whether the description
is shown too early. This lead to a DOMException and the description to never be shown.
Fix#2166
thanks for the report ❤️ . I could reproduce this also with Angular 12. This was in fact caused by an incorrect placement of a " in the number renderer. I opened a PR for this.
Note that we don't support Angular 15, yet. So you might run into other issues that are not bugs. See #2085.
The template had a bug closing the ngIf that checks whether the description
is shown too early. This lead to a DOMException and the description to never be shown.
Fix#2166
Describe the bug
Angular 15 + jsonforms 3.1.0
When a page with form is opened error appears in chrome console.
Reproduced only if
showUnfocusedDescription: true
and for fields withtype: number | integer.
In Chrome, Edge: ERROR DOMException: Failed to execute 'setAttribute' on 'Element': '||' is not a valid attribute name.
In Firefox: ERROR DOMException: String contains an invalid character
Pet app for reproducing.
https://github.com/dimpon/angular-with-jsonforms
Expected behavior
No errors in the console
Steps to reproduce the issue
Screenshots
No response
In which browser are you experiencing the issue?
Chrome Version 114.0.5735.199 (Official Build) (64-bit)
Which Version of JSON Forms are you using?
v3.1.0
Framework
Angular
RendererSet
Material
Additional context
No response
The text was updated successfully, but these errors were encountered: