Problem with namespaced data options in select #308
Replies: 5 comments
|
btw |
0 replies
|
Hello Peter,
Did you try to use wildcard selectors in there, so /*:X/*:X instead of
/X/X? That should at least tell us whether the problem is with namespaces.
Select does use a different way to evaluate template strings, but I do not
expect namespaces to be a thing.
KR,
Martin
…On Sun, 27 Jul 2025, 19:37 Peter Herkenrath, ***@***.***> wrote:
btw
for making some progress until the above problem is solved, I tried to
load the same data as json (no namespace ;-).
to get the select working I had to add a '?*' after the repeating prop
(the json demo on github uses a repeat ref without this)
—
Reply to this email directly, view it on GitHub
<#308 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGKEJEFTCI4DYYJTGROHNT3KUE3PAVCNFSM6AAAAACCNYLDUOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGOJQGI4DGMA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
0 replies
Answer selected by
pherk
|
I were used to wildcards in the times of betterforms, but I don't know why I did'nt try it with Fore |
0 replies
|
That looks like a clear bug. Thanks for finding it!
Could you open an issue? Interesting that its broken. Might be that using
no prefixes also works. There is an implicit namespace management that uses
the namespace/prefix pairs defined on the root of the loaded XML. A bit
implicit, but may be an acceptable work-around for now.
…On Sun, 27 Jul 2025, 20:16 Peter Herkenrath, ***@***.***> wrote:
I were used to wildcards in the times of betterforms, but I don't know why
I did'nt try it with Fore
... but it works with wildcards :-)
thank you for your prompt response, should I open an issue?
kind regards
Peter
—
Reply to this email directly, view it on GitHub
<#308 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGKEJFYM6CPHVCUBD6XSKL3KUJQHAVCNFSM6AAAAACCNYLDUOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGOJQGMYDAMI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
0 replies
|
using no prefixes w/o or with xpath-default-namespace does not work in select option template. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
the generated options have empty values. the labels are ok.
It seems that that the template expression are differently evaluated.
an suggestions?
a MWE
from dev-tools FireFox latest Ubuntu
the namespaced data are normally loaded from a server:
providers.xml
All reactions