I've tested the new 2.0.0-beta-1 and noticed, that there are as in 2.0.0-alpha-1 still many problems with Firefox, due to the issue described in TRINIDAD-1695. I hoped I could move from my special 2.0.0-alpha-1 with a patched Core.js to an official version. Could somebody implement the fix TRINIDAD-1695 on the 2.0 tree, please?
Regards Roland
