Thank you! That resolved my issue. Where can I find any additional notes on the
changes in the 1.5beta, or are most of these already in prior releases? Have
you added JSON support by any chance?
Thanks
Ryan
From: Alain Couthures
Sent: Tuesday, June 16, 2020 10:0
No problem. Did you see my answer about not being correct because instance element has to be in XForms namespace?
Le 16 juin 2020 à 18:57, Jay Straw a écrit :
BTW, this was XSLTForms 1.3, sorry I didn't mention that before.
On Sun, Jun 7
BTW, this was XSLTForms 1.3, sorry I didn't mention that before.
On Sun, Jun 7, 2020 at 11:54 PM Jay Straw
wrote:
> Sorry, just re-read my email, example #3 which worked was supposed to be
> this (copy and pasted #1 by mistake)
>
> http://www.w3.org/1999/xhtml";>
> http://www.w3.org/2002/xforms"
Both @nodeset and @ref are converted into @xf-ref because @nodeset is deprecated in XForms 2.0.
is to be replaced by
Le 16 juin 2020 à 15:28, Ryan Riley a écrit :
That makes sense. Thank you for your quick reply! I made a bit more progress
That makes sense. Thank you for your quick reply! I made a bit more progress,
then ran into an error trying to use dynamic labels within a select.
Uncaught TypeError: Cannot read property 'xpath_evaluate' of null
at XsltForms_binding.bind_evaluate (xsltforms.js:5576)
at XsltForms_itemset.
Because HTML5 attributes such as @selected are typed, XSLTForms 1.5beta has to avoid potential conflicts: except @id, @style and @class, every attribute for an XForms element is renamed with the "xf-" prefix for HTML5.
HTML5 also considers that custom elements cannot
I was delighted to find XSLTForms. I noticed you just published the 1.5beta
that supports HTML5 documents and have been trying to use it for a recent
project.
I was trying to determine whether I could load external XML files using
in an HTML5 document, but I receive an error with
this approac
