Community
Participate
Working Groups
After switching to XULRunner 1.9.1 the most frequent issue is that users with XULRunner 1.8 can't make any use of ATF. Let's try to relax the dependency on XULRunner 1.9.1 and provide at least basic functionality to those on older XULRunners and simple communication that would persuade them to actually update.
It turns out that I have XULRunner installed from two different sources, one from JBoss Tools, the other from ATF: Id: org.jboss.tools.xulrunner, Version: 1.0.0.GA-N200908061545-H145 Id: org.jboss.tools.xulrunner.feature.feature.group, Version: 1.8.1.3-20070904 Id: org.jboss.tools.xulrunner.feature.feature.jar, Version: 1.8.1.3-20070904 Id: org.jboss.tools.xulrunner.initializer, Version: 1.0.0.GA-N200908061545-H145 Id: org.mozilla.xulrunner, Version: 1.9.1.0_v20090825-0940 Id: org.mozilla.xulrunner.feature.feature.group, Version: 1.9.1.0_v20090825-1855-57Z379OhF77g7cFR37gN7 Id: org.mozilla.xulrunner.feature.feature.jar, Version: 1.9.1.0_v20090825-1855-57Z379OhF77g7cFR37gN7 Id: org.mozilla.xulrunner.gtk.linux.x86, Version: 1.9.1.0_v20090825-0940 Id: org.mozilla.xulrunner.gtk.linux.x86_64, Version: 1.8.1.4-20080112 Apparently version 1.8.1.4, provided by JBoss tools is preferred to ATF provided one because it matches my machine architecture. I'll try uninstalling it and see if it helps.
(In reply to comment #1) Whoops, wrong bug, I meant #292001