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

[Ernesto Baschny [cron IT]]

Am 20.05.2010 10:08, Steffen Gebert schrieb:
> Am 20.05.2010, 09:57 Uhr, schrieb Steffen Ritter <info at rs-websystems.de>:
> 
>> Am 20.05.2010 09:55, schrieb Popy:
>>> Hacks are (IMO) a cleaner way than a lot of possible classes on body tag
>>> which can't cover every browser and every browser version.
>> hacks per definition cannot be clean. that's what "hack states".
> +1 ;)
> 
>> +1 reading but I think the major version should be enough....
> Unfortunately not (always): E.g. FF3.6 some more very usefull CSS3 
> properties than 3.5

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?

Cheers,
Ernesto