Missing margin/padding on content element fields
Editing a content element in the backend currently shows some fields without margin/padding:
Updated by Ernesto Baschny about 7 years ago
The problem is the new order of loading of the CSS files.
normalize now comes before ext-all-notheme, where the margin:0/padding:0 is set for many elements (including fieldset). This used to be the other way around.
The problem is that ext-all-notheme also contains his own "reset" CSS (line 21) which now takes precedence over normalize (as it overwrites it).
What to do?
Easiest and most backwards compatible way would be to switch them around again (loading ext-all-notheme as a "library" even before normalize) to get back the old behaviour.