You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As reported by @Torcsi in eXist-db/exist#1420 and demonstrated by @dizzzz, given an element like <a b="&#34;c"/>, eXide returns this as
3.1.x / eXide returns <a b=""c"/>
whereas elsewhere this is returned with the ampersand properly escaped:
3.1.x / query via REST returns <a b="&#34;c"/>
3.1.1 / doc retrieval via REST returns <a b="&#34;c"/>
It appears that in eXide we return the literal string instead of serializing these strings. As a result, the browser is displaying & as &. Applying fn:serialize() to the strings should cause eXist to return &amp;#34;c which the browser will then display as the expected result, &34;c.
The text was updated successfully, but these errors were encountered:
As reported by @Torcsi in eXist-db/exist#1420 and demonstrated by @dizzzz, given an element like
<a b="&#34;c"/>
, eXide returns this aswhereas elsewhere this is returned with the ampersand properly escaped:
It appears that in eXide we return the literal string instead of serializing these strings. As a result, the browser is displaying
&
as&
. Applyingfn:serialize()
to the strings should cause eXist to return&amp;#34;c
which the browser will then display as the expected result,&34;c
.The text was updated successfully, but these errors were encountered: