Re: [Xsltforms-support] Different behaviour IE7 vs IE8 & FF3

[Javier D. <jd...@ge...>]

COUTHURES Alain escribió:
> Hello Javier,
>>
>> We tested the form with Firefox 3 and IExplorer 8 and all seemed to
>> work ok.
>>
>> But when using IExplorer 7, the following error appeared:
>>
>>
>>
>> And after that, another alert saying " 'length' is null or not an
>> object".
>>
>> We solved this error changing the name of instance from ppai to
>> ppai0, it seems IE7 it is not case sensitive.
> Thank you for pointing at this compatibility problem.
>
> It is true that there is almost no syntax check in XSLTForms. This was
> done at compile-time in AJAXForms with a Java program. But XSLTForms
> is much more concerned by performance so this should be added as an
> option.
>> This is not very problematic to us, but I think it should be
>> interesting that all browsers would work in the same way with the
>> same data, working ok or failing in all of then to avoid making all
>> tests in all browser versions.
> I know testing can required much time when not automatically performed...
>
> I'm not sure it would be a good idea to convert every id to lowercase,
> for example, and it should be performed at runtime in many different
> Javascript instructions anyway.
>
> It could be possible to convert every id into a string of
> ASCII/Unicode codes in Hex notation for maximal compatibility but is
> it really necessary???
I agree with you that it is not very interesting checking or converting
ids at runtime, because performance is a very important issue in xsltforms.
But it may be very useful that this and other checks should be activated
when running in debug mode to make easier debugging xsltforms. All
colleages that are using xsltforms are impressed and very happy with it,
but they say that sometimes is very difficult to find some errors in
code, because the errors generated are not very clear. For example, in
the error we sent you, we knew that there was an error in
"instance('ppai')/vct", but it took us some time to realize that the
problem was a name collision with other element due to the case issue in
IE7.

Best Regads,
Javier
>
> Thanks!
>
> -Alain