MathJax test results - 2013-05-01

10 views
Skip to first unread message

Frédéric WANG

unread,
May 1, 2013, 3:14:48 PM5/1/13
to mathj...@googlegroups.com

Davide P. Cervone

unread,
May 1, 2013, 3:34:26 PM5/1/13
to mathj...@googlegroups.com
Great, thanks! I was checking them as they ran, and the non-IE ones looks clean. I fixed one problem with the missing-children test, but other than that, they look good.

I haven't gone through the IE tests fully yet, but will let you know when I do.

Davide
> Frédéric Wang
> maths-informatique-jeux.com/blog/frederic
>
> --
> You received this message because you are subscribed to the Google Groups "MathJax Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to mathjax-dev...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

Davide P. Cervone

unread,
May 1, 2013, 3:57:02 PM5/1/13
to mathj...@googlegroups.com
Looks like there is something wrong in the SVG code that is tripping up IE9. I'll have to look into that.

Davide


On May 1, 2013, at 3:14 PM, Frédéric WANG wrote:

Davide Cervone

unread,
May 1, 2013, 6:28:13 PM5/1/13
to mathj...@googlegroups.com
The IE9-SVG tests seem to be running in Quirks mode rather than IE9-
standards mode, and that is the cause of the Math Processing Errors,
since SVG is not supported except in IE9-standards mode. I see that
browserMode is IE9, but I suspect the documentMode is not IE9-
standards. It usually requires a <meta> tag or an appropriate DOCTYPE
in the file to force the documentMode, and that doesn't happen for me
in my tests by hand (not sure what the framework does about that). In
any case, the errors that are occurring indicate that it is not
running in IE9-standards mode. When I switch to IE9 standards by
hand, that eliminates the math processing errors. I'm wondering if
the IE8 and IE7 tests are also running in quirks mode rather than
their standards modes. IE testing is always a trial.

The only error that I actually identified was:

API/Ajax/Load-2.html
API/Ajax/Require-2.html

When the file that defined f() fails to load (as it does in Quirks
mode), then f is undefined and you get this error message. It works
for me in IE9 mode (though test 3 fails). I'm wondering if forcing
IE9 mode isn't working?

You could define

var f = function (x) {return 1}

so that f is always defined (and gets redefined when the file loads).

I also see that the localization substitutions don't work in IE other
than IE9-standards mode, so I have to look into that.

Davide


On May 1, 2013, at 3:14 PM, Frédéric WANG wrote:

Frédéric WANG

unread,
May 2, 2013, 4:56:19 AM5/2/13
to mathj...@googlegroups.com
OK, that's also what I suspected when you said that you found the extra
comma error, while it also appeared in IE9...

The testing framework just simulates keyboard actions to display the
developer tools and switch to Quirks/IE7/IE8/IE9 document mode so no
need for a <meta> tag (as we discussed in the past, we would otherwise
need to provide four versions of the testsuite or something to generate
these versions). Unfortunately, there is still no way to do that
directly: http://code.google.com/p/selenium/issues/detail?id=2564

The document mode is changed at startup and then is preserved for the
rest of the test pages... at least that worked in IE9. IE was
automatically upgraded to IE10 and it seems that things are no longer
working as expected. I still see the change of document mode but
apparently this is not preserved. I'll see if I can downgrade back to IE9.

On 02/05/2013 00:28, Davide Cervone wrote:
> The IE9-SVG tests seem to be running in Quirks mode rather than
> IE9-standards mode, and that is the cause of the Math Processing
> Errors, since SVG is not supported except in IE9-standards mode. I
> see that browserMode is IE9, but I suspect the documentMode is not
> IE9-standards. It usually requires a <meta> tag or an appropriate
> DOCTYPE in the file to force the documentMode, and that doesn't happen
> for me in my tests by hand (not sure what the framework does about
> that). In any case, the errors that are occurring indicate that it is
> not running in IE9-standards mode. When I switch to IE9 standards by
> hand, that eliminates the math processing errors. I'm wondering if
> the IE8 and IE7 tests are also running in quirks mode rather than
> their standards modes. IE testing is always a trial.
>
> The only error that I actually identified was:
>
> API/Ajax/Load-2.html
> API/Ajax/Require-2.html
>
> When the file that defined f() fails to load (as it does in Quirks
> mode), then f is undefined and you get this error message. It works
> for me in IE9 mode (though test 3 fails). I'm wondering if forcing
> IE9 mode isn't working?
>
> You could define
>
> var f = function (x) {return 1}
>
> so that f is always defined (and gets redefined when the file loads).
>
> I also see that the localization substitutions don't work in IE other
> than IE9-standards mode, so I have to look into that.
>
> Davide
>

Reply all
Reply to author
Forward
0 new messages