Hi Ate,
Thanks for your reply. I think I could help with these issues, and close the
gap for full compliance of the js language model.
I was wondering, did you have a timeline in mind for the 2.0 release? I should
start to free up in June/July.
Let me know what you think. Thank you,
Jake
> On Apr 18, 2019, at 3:46 PM, Ate Douma <a...@douma.nu> wrote:
>
>
>
>> On 18/04/2019 18.00, Jacob Beard wrote:
>> Hi Ate,
>>> On Apr 18, 2019, at 11:23 AM, Ate Douma <a...@douma.nu> wrote:
>>>
>>> Only for the javascript language (using Java 8 Nashorn, now deprecated
>>> since Java 11...) there are still 3/188 W3C IRP tests failing.
>>> And those 3 test failures are really, really difficult to fix, because
>>> of limitations/quirks in the Nashorn engine itself.
>> Could you please provide more information on this? Which tests are failing,
>> and what are the limitations and quirks of Nashorn that cause this?
>
> Sure.
>
> Regarding 'quirks': see issue SCXML-273 [1] which concerns the problem
> that the Nashorn engine by default doesn't fail on referencing a missing
> property. Which is tested by W3C IRP test 307.
>
> Regarding limitations: there are two W3C IRP ecma test, 557 and 561,
> which make use of XML DOM APIs in a condition, like:
>
> cond="var1.getElementsByTagName('book')[0].getAttribute('title') == 'title1'"
>
> However Nashorn doesn't provide default/native XML DOM support, and
> adding that would be (at least from my perspective) quite an effort, if
> even properly doable.
> That doesn't feel like worth the effort, with little added value/ROI.
>
> [1] https://issues.apache.org/jira/browse/SCXML-273
>
>> Thank you,
>> Jake
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
>> For additional commands, e-mail: user-h...@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org
