Dear all,
 
Thanks all for your support, as we (in HtmlUnit) are continuously enhancing 
javascript, we arrive to many cases that must be handled at Rhino level.
 
As you know, our reference is the real browsers (FF/IE) even if it doesn't 
comply 100% to the specs, e.g. 
https://bugzilla.mozilla.org/show_bug.cgi?id=370279.
 
Now, as Marc said, we are considering forking, as our dependencies (other 
projects or end users) don't care much about which version of Rhino is used, 
and it seems there is a general delay in fixing issues.
 
Please also note that we are willing to provide any help needed.
 
Below are our current issues:
https://bugzilla.mozilla.org/show_bug.cgi?id=370279
https://bugzilla.mozilla.org/show_bug.cgi?id=368019
https://bugzilla.mozilla.org/show_bug.cgi?id=412247
https://bugzilla.mozilla.org/show_bug.cgi?id=392593
https://bugzilla.mozilla.org/show_bug.cgi?id=369860
https://bugzilla.mozilla.org/show_bug.cgi?id=389278
https://bugzilla.mozilla.org/show_bug.cgi?id=390659
https://bugzilla.mozilla.org/show_bug.cgi?id=374918 (we have a workaround)
 
Thanks again, and please consider the cumulative dependencies behind the beast.
 
Yours,
Ahmed Ashour


      
____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 
_______________________________________________
dev-tech-js-engine-rhino mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino

Reply via email to