[TYPO3-core] RFC #14442: Backend lacks a clean way for CSS browser conditions

[Steffen Gebert]

Am 20.05.2010, 10:37 Uhr, schrieb Ernesto Baschny [cron IT]  
<ernst at cron-it.de>:

> I am no BE design expert, but I feel that we shouldn't use browser  
> specific features in our backend which are not standard. So even if they  
> are "useful", we won't probably use them.
>
> Then we would only need "fixes" where CSS properties works different in  
> different browsers and I guess that this could be done from case to case  
> basis.
>
> Adding browser specific classes in the header will end up having the CSS  
> authors become "lazy" and just CSS for each browser individually. This  
> isn't maintainable, testeable and not a direction I want to go.
>
> What do BE specialists think about it?

I feel the opposite :)

I planned to use CSS3 / data-uri for the backend restyling, resulting in  
fu***ing browser showing no background-gradients or tiny decoration  
graphics- but still being usable.
HCI team / designer told me, that BE has to look the same everywhere.

As I'm against loading 100 10byte-shadows, I/we decided using modern  
techniques and later overwrite the rules, which e.g. add a background  
gradient for unable browsers (determined by the CSS classes) with a  
background image.

That's why this RFC is here.

Steffen