Opera XMLHttpRequest - a big dissapointment and shame for quality assurance and project leaders

[Marek Mänd]

I am very dissapointed that you shipped buggy Javascript XMLHttpRequest
object in Opera8.0 final. Many people pointed out on its errors in
implementation, yet it still gives double results in response by
generating inapropriate events.

http://jibbering.com/2004/9/opera-xmlhttp-bug1.html

Opera, by spawning such an object opened another eternal javascript code
workarounding hell. Very bad.

[Andrew Gregory]

The "double event" only occurs on very small files. What's happening is
that Opera queues a readyState=3 event, but before that is processed the
transfer completes, readyState is set to 4, and another onReadyStateChange
event queued. I've found once the file size goes above about 500 bytes,
there's no problem.

--
Andrew Gregory
<URL: http://www.scss.com.au/family/andrew/ >

[Oivind Kolloen]

Also, the missing methods from the XMLHttpRequest object (ie
setRequestHeaders). Not only do you have to check if the object is there
in the first place, you also have to check if it supports the right
methods.

A real shame, I had looked forward to be able to tell people to go for 8.0
and be able to drop a lot of workaround code. Instead I have to make even
more workaround code.

Oivind K.

--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

[Marek Mänd]

Oivind Kolloen wrote:
> On Wed, 20 Apr 2005 11:12:58 +0200, Marek Mänd <cador...@mail.ee> wrote:
>
>> I am very dissapointed that you shipped buggy Javascript
>> XMLHttpRequest object in Opera8.0 final. Many people pointed out on
>> its errors in implementation

...

>> Opera, by spawning such an object opened another eternal javascript
>> code workarounding hell. Very bad.
> Also, the missing methods from the XMLHttpRequest object (ie
> setRequestHeaders). Not only do you have to check if the object is
> there in the first place, you also have to check if it supports the
> right methods.
> A real shame, I had looked forward to be able to tell people to go for

> 8..0 and be able to drop a lot of workaround code. Instead I have to

> make even more workaround code.

I dont wonder at all about things that are about Javascript. I even
hoped it will go so, so that way I wouldnt be wrong when I told myself -
my gut feeling says: they never make it usable for version 8. Opera has
had in many past years always little focus on javascript area and one
reason why to increase major version number might have been
'revolutionary and to Opera newly presented' XMLHttoRequest. In which
promised delivery they failed.