[TYPO3-core] RFC: #14201: getBrowserInfo delivers wrong info

Lars Houmark lars at houmark.com
Wed Apr 28 11:34:21 CEST 2010


Francois Suter wrote:

> In theory, yes. I don't want to start a whole debate here, but I guess
> you can see the difference between patches that fix something that
> doesn't work at all and patches that fix a working, but buggy behavior
> (thus changing it). Anyway, it's not my call, it's Olly's. I just wanted
> to point this out.

I don't wont to start a debate either, but;

If it is buggy, ie. returning the wrong information, when it's sole 
purpose is to return the correct value, is it then working? ;)

I guess what I mean is that we cannot expect one single sane person to 
use 'netscape' as a serious value for the current implementation, so why 
should we block all the rest of the world from being able to use this 
feature in the current stable branch?

In addition, adding it to NEWS.txt should inform anyone that they can 
now expect the RIGHT value and if they are using 'netscape' for any 
reason, the need to change their TS a bit.

-- 
Lars Houmark



More information about the TYPO3-team-core mailing list