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
When the Add another component is rendered in an app some styles can become over-written by more generic styles in use on the page on which it appears. A specific example of this is shown in the screenshots below, which also shows a temporary solution. Affected in this example is the "Delete" button.
The cause of this is that if the stylesheets are loaded in the expected order (alphabetical) then the styles for the component are loaded before those of the "Button" component which therefore take precedence and has the effect of eliminating the top margin value for the "Delete" button.
The solution would probably be to wrap the selector for this element with a reference to its parent element so that it has greater specificity.
Correct layout
Faulty layout
The text was updated successfully, but these errors were encountered:
When the Add another component is rendered in an app some styles can become over-written by more generic styles in use on the page on which it appears. A specific example of this is shown in the screenshots below, which also shows a temporary solution. Affected in this example is the "Delete" button.
The cause of this is that if the stylesheets are loaded in the expected order (alphabetical) then the styles for the component are loaded before those of the "Button" component which therefore take precedence and has the effect of eliminating the top margin value for the "Delete" button.
The solution would probably be to wrap the selector for this element with a reference to its parent element so that it has greater specificity.
The text was updated successfully, but these errors were encountered: