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
If the editor's HTML markup contains inline CSS styles, and a CSS attribute value includes a semicolon (;), it breaks the applied styles and throws an exception.
For example: <p style= "" ....background-image: url('data:image/png;base64...;""
Currently, semicolons are only accepted as separators between CSS style attributes, and they are not supported within the value of a CSS property.
The bug is in the common package that we inherit from the kendo-editor-common repo.
When inline CSS contains a semicolon (;) within a value (e.g.,
), the Kendo Editor fails to parse it correctly, breaking styles and throwing an exception.
Expected Behavior
The editor should consider semicolons in CSS values as part of the value instead of as separators. It should apply the styles correctly and handle any invalid CSS smoothly by giving a clear error message while keeping the content intact.
The text was updated successfully, but these errors were encountered:
Related to private issue
Description
If the editor's HTML markup contains inline CSS styles, and a CSS attribute value includes a semicolon (;), it breaks the applied styles and throws an exception.
For example: <p style= "" ....background-image: url('data:image/png;base64...;""
Currently, semicolons are only accepted as separators between CSS style attributes, and they are not supported within the value of a CSS property.
The bug is in the common package that we inherit from the kendo-editor-common repo.
Steps To Reproduce
https://stackblitz.com/edit/angular-i2nq1a?file=src%2Fapp%2Fapp.component.ts
Actual Behavior
When inline CSS contains a semicolon (;) within a value (e.g.,
), the Kendo Editor fails to parse it correctly, breaking styles and throwing an exception.Expected Behavior
The editor should consider semicolons in CSS values as part of the value instead of as separators. It should apply the styles correctly and handle any invalid CSS smoothly by giving a clear error message while keeping the content intact.
The text was updated successfully, but these errors were encountered: