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
As of #3442, we check for CSS that cannot be inlined into <style> tags (e.g. because it contains the string </style>, which could could cause an XSS vulnerability).
Right now we pay this cost during SSR, but ideally this validation should be done once during compilation, not multiple times during SSR. However, this would be a breaking change, since it could impact existing LEX components (which currently don't need to support SSR).
Another solution would be to find some other solution entirely that doesn't involve validating the <style> contents. (E.g. figuring out a clever way to escape a CSS selector like [attr="</style>"], assuming that this pattern even exists in the wild.)
The text was updated successfully, but these errors were encountered:
As of #3442, we check for CSS that cannot be inlined into
<style>
tags (e.g. because it contains the string</style>
, which could could cause an XSS vulnerability).Right now we pay this cost during SSR, but ideally this validation should be done once during compilation, not multiple times during SSR. However, this would be a breaking change, since it could impact existing LEX components (which currently don't need to support SSR).
Another solution would be to find some other solution entirely that doesn't involve validating the
<style>
contents. (E.g. figuring out a clever way to escape a CSS selector like[attr="</style>"]
, assuming that this pattern even exists in the wild.)The text was updated successfully, but these errors were encountered: