10,853
edits
Salesforce admins: Urgent action required!
Style editor: Difference between revisions
Jump to navigation
Jump to search
→Style hierarchy
| Line 22: | Line 22: | ||
The styles are organized in a hierarchy. The best practice when defining new styles is to select a style closest to the one you want to use and click '''Add'''. This creates a child style that uses the properties of its parent until you change them. | The styles are organized in a hierarchy. The best practice when defining new styles is to select a style closest to the one you want to use and click '''Add'''. This creates a child style that uses the properties of its parent until you change them. | ||
When you modify a property in the parent style, and the child style does not have its own definition of the property, parent change is used. However, when you modify a property in the child style, the link to the parent is | When you modify a property in the parent style, and the child style does not have its own definition of the property, parent change is used. However, when you modify a property in the child style, the link to the parent is broken for that property. Any further changes for the property in the parent no longer apply to the child. | ||
In Woodford, the style editor also includes a revert button next to a style property. It allows you to undo customization in the child style, reverting to the parent value. For top-level styles, you can revert to the built-in defaults. | In Woodford, the style editor also includes a revert button next to a style property. It allows you to undo customization in the child style, reverting to the parent value. For top-level styles, you can revert to the built-in defaults. | ||