I don't know what you've done so far in this aspect but I looked into
a few tests (Opera 9, Windows XP).

testFormActivating: passed for me

All three errors that this test throws are caused by a problem with
hasAttribute('method').  It looks like if you don't specify a method
for the form, then Opera automatically assigns it to "get".  And the
current test setup is expecting there to be no attribute 'method' and
for the Ajax.Request to default it to "post".  This looks like an
unsolvable problem so we would have to change the tests to accommodate

element.getAttribute('title') returns null directly from Opera and the
test expects it to be blank.  We will probably need to check for this
case and fix it to be similar across browsers.

Looks to be a problem with grabbing the width from an element that has
display:none.  Opera doesn't return "auto" as prototype is expecting
but "0px".


On Feb 10, 8:23 pm, "Tobie Langel" <[EMAIL PROTECTED]> wrote:
> Hi,
> AlthoughOpera9 is *not* officially supported by Prototype, it passes
> nearly all tests.
> It would be great to be able to officialy supportOpera9 in upcoming
> versions of Prototype.
> This would at least imply dealing with the currently failing tests.
> Here's a list forOpera9.02 (on Mac OSX 10.4).
> in form.js:
> * testFormActivating and
> * testFormRequest.
> in position.js:
> * testWithin.
> in dom.js:
> * testElementUpdateInTableRow,
> * testElementUpdateInTable,
> * testElementGetStyle and
> * testElementReadAttribute.
> As you see, there's not that much to do (although there might be other
> issues that the unit tests don't cover).
> So if anybody is willing to help me out on this issue, that would be
> very much appreciated.
> Tobie

You received this message because you are subscribed to the Google Groups 
"Prototype: Core" group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 

Reply via email to