WordPress.org

Make WordPress Core

Opened 18 months ago

Last modified 4 weeks ago

#26350 new defect (bug)

!important audit

Reported by: azaozz Owned by:
Milestone: Future Release Priority: high
Severity: major Version: 3.8
Component: Administration Keywords:
Focuses: ui, performance Cc:

Description

After the MP6 merge many CSS rules became "very !important". Some are so !important that overwrite other !important...

Looking at wp-admin.css: in trunk there are 65 !important compared to 22 in 3.7.

Attachments (2)

26350.diff (61.7 KB) - added by adamsilverstein 6 months ago.
remove all !important statements from css
26350.2.diff (45.1 KB) - added by adamsilverstein 4 weeks ago.
refresh

Download all attachments as: .zip

Change History (9)

comment:1 follow-up: @Rhomanu18 months ago

66 in 3.8.

Agreed, it's not a good practice : Using these force the use of another !important to overwrite a rule, and then it's expanding... While it's just a simple problem of CSS declaration weight.

But it will be long to fix... I'll try a bit tonight (I must find how to contribute without blocking others' work), but there's many CSS files to check.

comment:2 in reply to: ↑ 1 @bassgang18 months ago

Hi Rhomanu,

I also want to look into this but do not want to make the work twice, any proposal how to divide it, any progress at your site so far?

comment:3 @azaozz18 months ago

  • Milestone changed from 3.8 to Future Release

Yeah, each use of !important spreads exponentially. Every time it needs to be overridden, new !important has to be used.

As much as I'd like to get rid of all !important for 3.8, there is simply not enough time to do it... Hoping we can do this in 3.9.

comment:4 @nacin16 months ago

  • Component changed from General to Performance

comment:5 @nacin16 months ago

  • Component changed from Performance to Administration
  • Focuses performance added

@adamsilverstein6 months ago

remove all !important statements from css

comment:6 @adamsilverstein6 months ago

26350.diff: Is anything really that !important? and if so, why? This patch removes all !important declaration, please restore where appropriate, with !justification.

@adamsilverstein4 weeks ago

refresh

comment:7 @adamsilverstein4 weeks ago

Refresh against trunk.

Left in one !important where the purpose was indicated in a doc block.

Note: See TracTickets for help on using tickets.