[TYPO3-core] RFC: 10964: ExtJs prototype-adapter leads to several IE-errors

[Steffen Kamper]

Hi Dmitry,

Dmitry Dulepov schrieb:
> Hi!
> 
> Dmitry Dulepov wrote:
>> -1. There is no need to force this on people. Give them the choice :)
>> Keep the adapter because some people may need it. If you remove it,
>> people will have to install an alternative copy somewhere. Shipping
>> ExtJS with core allows people to rely on it. If you limit the copy,
>> you limit the relation. There is no advantage.
>>
>> It does not hurt to have this file. Just do not use it for core.
> 
> May be a use case will help to understand it better.
> 
> I had a project where I had to use effects. ExtJS does not provide enough of them, so I used Scriptaculous. Scriptaculous needs Prototype. To minimize the whole stuff I used the Prototype adapter, which worked very well for that project. Changing it to Ext adapter would only increase JS download size but will not provide any advantages. So the optimal choice for certain projects will be the Prototype adapter.
> 

that was my first thought too. But obviously the prototype adapter 
doesn't seem to work well for IE especially. May be we found an 
unfriendly combination in core where this get obvious.
So second thought was to prevent others who are not aware of this 
problem to use it, they may run in the same problem and don't know how 
to fix.
So i'm 50/50 to this.
BTW - in extJs 3 also jquery adapter is included, in 2 also yui adapter. 
Do you think we should include all adapters even if we don't use them?

vg Steffen