Comment 11 for bug 787561

As far as I am aware, the bug has crawled back under its rock -- it has been *completely* absent since I set things up to use the 10.0.12 and more recently the 17.0.3 *Linux* versions of xulrunner on our CentOS 5.9 (32-bit) Linux systems. Presently we are using the 2.3.cwmars101 version of the staff client. The bug might still be there, but maybe the newer versions of xulrunner reduce the exposure of the conditions that trigger it. What verison of xulrunner is shipped with the C/W Mars Staff Client installer? I can't tell -- when run under Wine, xulrunner just displays boxes instead of its version number, but given the number of boxes, I am guessing 1.9.x... I wonder if it makes sense to ship a newer version of xulrunner. Note the application.ini file indicates that the max version is 14.*, but the staff client is happy with xulrunner 17.* and according to the developers, even newer versions should work as well (it has appearently been tested with version 19).