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
I've encountered an issue with the inline CSS optimization feature of the LiteSpeed Cache plugin. It appears that the plugin's CSS optimization process is not handling inline <style> tags correctly when the CSS contains the < character, such as in CSS @property syntax.
Issue Description:
The inline CSS within <style> tags that include CSS properties with syntax like @property --image-title-bg{syntax:'<color>'; ...} or list-style-image: url('data:image/svg+xml;utf8,<svg xmlns... are not being optimized to all css in <style>. It seems that the < character is causing the regex pattern used for matching and optimizing inline CSS to terminate prematurely.
Actual Behavior:
The inline CSS is not optimized, and the CSS content after the < character seems to be ignored by the optimization process.
I tried to change the matching code to the following code, and it can be matched for the time being. I hope you can help me update to solve the problem.
I hope this information is helpful for diagnosing and resolving the issue. Please let me know if you need any further details or if I can assist in any way.
Thank you.
The text was updated successfully, but these errors were encountered:
I've encountered an issue with the inline CSS optimization feature of the LiteSpeed Cache plugin. It appears that the plugin's CSS optimization process is not handling inline
<style>
tags correctly when the CSS contains the<
character, such as in CSS@property
syntax.Issue Description:
The inline CSS within
<style>
tags that include CSS properties with syntax like@property --image-title-bg{syntax:'<color>'; ...}
orlist-style-image: url('data:image/svg+xml;utf8,<svg xmlns...
are not being optimized to all css in<style>
. It seems that the<
character is causing the regex pattern used for matching and optimizing inline CSS to terminate prematurely.Actual Behavior:
The inline CSS is not optimized, and the CSS content after the
<
character seems to be ignored by the optimization process.I tried to change the matching code to the following code, and it can be matched for the time being. I hope you can help me update to solve the problem.
I hope this information is helpful for diagnosing and resolving the issue. Please let me know if you need any further details or if I can assist in any way.
Thank you.
The text was updated successfully, but these errors were encountered: