[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
> [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
Thanks,
Norris
You are viewing a mobilized version of this site...
View original page here