1 cset was pushed to core/commerce: As we use xmlhttp extensively, a weird b...
marcel-111RdWWlOxkOkXtL6OYfHgC/[email protected] (Marcel van der Boom)
| Newsgroups | gmane.comp.cms.xaraya.bk-notices |
|---|---|
| Organization | Xaraya |
| Message-ID | <[email protected]> |
Changes were applied by marcel to core/commerce level 15.
The following cset was applied:
ChangeSet
1.1994 05/06/09 19:13:31 [email protected] +1 -0
As we use xmlhttp extensively, a weird bug showed up here for safari. I think safari is wrong here, but not sure. Working around it at the expense of a possible loss of error
information when something really goes wrong. When it does, the exception handler should kick in, but i have no idea how to test this quickly.
html/modules/base/xartemplates/includes/xmlhttprequest.js
1.5 05/06/09 19:13:29 [email protected] +6 -3
- displaying the alert might be bit early (safari at least resubmits it, so it would show the alert while the action still will succeed)
Adding a note to describe this. Feels like a hack in the xmlhttp implementation where safari is too fast. Making the exception alerts
stand out.
Links for the differences:
http://xaraya.com:15000/core/commerce/[email protected]