Paul,
I will restore a compatible behavior in next commit.
I am testing an extension for load action: if the node type is
xforms:HTMLFragment, it will directly load the node content and not perform an
HTTP request for getting it for the node content. It was not a good idea to
restrict to xsd:anyURI type the previous behavior.
Please tell me if you are in a hurry.
-Alain
> Le 30 janvier 2014 à 01:14, Paul Vanderveen <[email protected]> a écrit
> :
>
>
> We are in the process of updating to rev. 586 code that supports IE11 (among
> other things)
>
> One thing I have noticed is that the xf:load element behavior has changed.
>
>
>
> Given the following simplified XML model:
>
> <Data>
>
> <RunMethod>javascript:alert(‘Hello there’)</RunMethod>
>
> </Data>
>
>
>
> The following shorthand used to work:
>
> <xf:load ref=”/Data/RunMethod”>
>
>
>
> This no longer works, so after some experimentation I was able to get it to
> work by refactoring to:
>
> <xf:load>
>
> <xf:resource value=”/Data/RunMethod”/>
>
> </xf:load>
>
>
>
> We had quite a few forms that used the shorthand that will be affected. My
> question is whether the shorthand was valid XForms, or if XSLTForms
> intentionally removed it.
>
>
>
>
>
> Paul Vanderveen
>
------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable
security intelligence. It gives you real-time visual feedback on key
security issues and trends. Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
_______________________________________________
Xsltforms-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xsltforms-support
