Rhino "fork": htmlunit-core-js
Marc Guillemot
[cross post on Rhino & HtmlUnit-dev mailing lists]
as discussed for some time on the Rhino mailing list, we (the HtmlUnit
project) have now started our Rhino fork. The main motivation is to be
able to fix problems that we currently have with Rhino and for which no
workaround is possible "from outside".
http://htmlunit.svn.sourceforge.net/viewvc/htmlunit/trunk/core-js/
I wish that we will be able to close this project in a not too far
future, once all issues that matter for us are fixed in Rhino. For this
purpose we will continue to open issues and provide patches reflecting
the changes we will make in htmlunit-core-js. Nevertheless I understand
that Rhino committers' priorities are a bit different than ours (for
instance being able to reproduce browser behavior is more important for
us than speed) and that the patches we propose may not get applied.
Cheers,
Marc.
--
Blog: http://mguillem.wordpress.com
Norris Boyd
On the Rhino side, I have been working to make changes needed by
HTMLUnit and thus remove the need for a continuation of the fork. In
particular, I want to allow for pluggable Map classes to implement
JavaScript objects, which would allow for HTMLUnit to choose slower,
browser-compatible behavior while others can choose faster behavior. I
know I've been a bit slow in getting these things done and appreciate
the need for HTMLUnit to have a place to make their changes quickly.
Thanks,
Norris