function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
navya m 23navya m 23 

Summer 18 Release's css changes are reflecting in custom components though we used old version of static resource for LDS styling.How is it possible

We use SLDS version <link rel="stylesheet" type="text/css" href="{!URLFOR($Resource.SLDS0110, 'assets/styles/salesforce-lightning-design-system-vf.css')}" /> our application.Due to recent changes in Summer 18 Release in css,few functionality failed due to css changes that salesforce has introduced in release.My doubt is how are the changes getting reflected in custom Lightning components as we have not updated SLDS version in static resource.Can somebody help me clear this .
Chris Bacon 4Chris Bacon 4
I have had this before I believe the answer is that your components are also being served the latest SLDS by the one.app container, as far as i know you cant prevent this. What your likely seeing is conflicting classes in the stylesheets and the latest SLDS is taking precedance.
navya m 23navya m 23
Thanks @chris Bacon