When did inline CSS usage become a security concern in managed packages?
Answer
Inline CSS usage became a security concern in managed packages because it is incompatible with style isolation and can lead to vulnerabilities like clickjacking. To address this, developers are required to use static resources for CSS, ensuring secure and isolated styling within the Salesforce framework.
When did inline CSS usage become a security concern in managed packages?
Recommended Answer Update
Inline CSS usage became a security concern in managed packages because it's incompatible with style isolation and can lead to vulnerabilities like clickjacking. To address this, you'll need to use static resources for CSS, ensuring secure and isolated styling within the Salesforce framework.
Reasoning
The existing answer is accurate and comprehensive but could be improved with more conversational tone per the style guidelines. The main change is replacing 'developers are required to' with 'you'll need to' to make it more direct and user-focused, while maintaining all existing technical points and information. I selected LoadCSSApexStylesheet and LoadCSSLinkHref as related rules because this FAQ directly addresses the security concern of inline CSS usage - both rules detect when CSS is being loaded in ways that could bypass proper security isolation. LoadCSSApexStylesheet detects Apex:stylesheet usage which can load external CSS, and LoadCSSLinkHref detects link href CSS loading - both are alternatives to inline CSS that the FAQ recommends using static resources instead of.