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

[Steffen Kamper]

Jigal van Hemert schrieb:
> Steffen Kamper wrote:
>> Jigal van Hemert schrieb:
>>> Steffen Gebert wrote:
>>>> Problem:
>>>> We currently have no clean way to provide browser-specific CSS in BE.
>>>>
>>>> Solution:
>>>> Add a few classes to the body tag, dependent on the HTTP user agent, 
>>>> like
>>>
>>> -1 because t3lib_utility_Client::getBrowserInfo() is buggy. Depending 
>>> on this function can easily destroy the BE layout. The IE8 on my 
>>> Vista installation is for example detected as IE6 by this function.
>>>
>>
>> it's not buggy, that's it what browser sends. If your IE8 sends IE6 
>> you may be in compatibility mode.
> 
> I didn't mean to hurt your feelings, but if it doesn't detect the 
> browser correctly in two cases (Chrome is seen as Safari) on a single 
> computer then I must conclude it's buggy (sorry).
> 
> Checked this, but IE is *not* in compatibility mode.
> 
> It simply sends the user agent string:
> Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0; 
> Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) ; SLCC1; .NET 
> CLR 2.0.50727; .NET CLR 1.1.4322; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
> 
> So it reports that it is MSIE 8.0, but getBrowserInfo() decides to use 
> the last name/version it finds. Therefore it detects is as MSIE 6.0.
> 
> As already pointed out in the other thread in the dev list, [1] has a 
> list of many user agents as seen "in the wild".
> 
> [1] http://chrisschuld.com/proj/Browser/useragents.txt
> 

did you debugged the delivered array? It has the latest one in "browser" 
but has all in "all" key of array.
The "browser" is used for ts for compatibility, but now that is fixed, 
it makes a search in all array. Did you tried / debugged?

vg Steffen