Loading...
 
Skip to main content

Unified admin backend CSS scope is too wide

  • Tracker item actions
Trackers
Items
Status
Open
Subject
Unified admin backend CSS scope is too wide
Version
24.x
Category
  • Conflict of two features (each works well independently)
Feature
Admin Interface (UI)
Resolution status
New
Submitted by
Gary Cunningham-Lee
Lastmod by
Gary Cunningham-Lee
Rating
(0)
Related-to
Description

Even when the new unified admin backend isn't turned on, adminui.css is active and imposes style details like link color that conflict with the active theme stylesheet in many cases.

I suggest the page elements of the new backend be given a unique parent class to distinguish them from, for example, the standard navbar that appears in the top or topbar zone when the new backend isn't active, so its CSS rules aren't erroneously applied.

Alternatively, adminui.css could just not be activated unless the feature is.

(Actually, IMO adminui.css (the visual rules like foreground and background colors, etc.) should be a theme (or two - light and dark) that can be selected, or a standard theme selected consistent with the "make it optional" rule. The adminui appearance could be the default for new installations, but could then be deselected for sites where maybe organization or corporate branding is a priority (and at sites that live on the wild side and don't need black and white menus 😉 ).

Importance
8
Easy to solve?
5
Priority
40
Demonstrate Bug on Tiki 19+
Demonstrate Bug (older Tiki versions)
Ticket ID
8004
Created
Friday 24 December, 2021 09:49:11 UTC
by Gary Cunningham-Lee
LastModif
Friday 24 December, 2021 09:49:11 UTC


Show PHP error messages