https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37054
--- Comment #60 from David Liddle <[email protected]> --- (In reply to David Cook from comment #58) > I know I keep saying this, but if we have these override CSS variables it > would be very clean. > > (I suppose we could look too at the timing. Do we want these settings to be > able to override OpacUserCSS or should OpacUserCSS override these?) Hi there... as I read your questions, it occurred to me as a system administrator that: 1. If you have UI color scheme settings override OpacUserCSS, then it might need to be an all-or-nothing, one-or-the-other approach. Allowing one to override some aspects of the other, but not all, could create headaches for people. 2. I'm only guessing here, but people who choose to modify the styling with the UI may be less likely to know that OpacUserCSS exists. If the latter overrides the former, then they're going to be left wondering why their settings didn't take effect. 3. A notice (or alert) in each location would aid staff and/or users with the above conditions. For example, if OpacUserCSS overrides UI, then a notice in the UI settings might state, "Your choice(s) here will not be applied because OpacUserCSS is populated." Or the choices may be grayed out and unavailable. If UI overrides OpacUserCSS, then the converse could be true. At OpacUserCSS, one might read, "This setting is unavailable because a color scheme other than the default has been selected." -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
