Re: [Xsltforms-support] hiding/displaying groups

[Alain C. <ala...@ag...>]

Hello Jens,
> I have groups for hiding/displaying a set of buttons for inserting missing elements and attributes. They are at times monstrously long, such as,
>
> <xf:group class="show-hide" ref=".[not(@altRepGroup)] | .[not(@authority)] | .[not(@authorityURI)] | .[not(@displayLabel)] | .[not(@ID)] | .[not(@lang)] | .[not(@nameTitleGroup)] | .[not(mods:nonSort)] | .[not(mods:partName)] | .[not(mods:partNumber)] | .[not(@script)] | .[not(mods:subTitle)] | .[not(@supplied)] | .[not(mods:title)] | .[not(@transliteration)] | .[not(@type)] | .[not(@usage)] | .[not(@valueURI)] | .[not(@xml:lang)] | .[not(@xlink:href)]">
First, I would try to minimize such expressions like this, if there is 
one char that should not appear in values:
.[not(contains(concat('~',@altRepGroup,'~',@authority,'~',@authorityURI,'~',@displayLabel,'~',@ID,'~',@lang,'~',@nameTitleGroup,'~',.....,'~'),'~~'))] 

>
> My problem is that this works with fine with xsltforms-1.0RC, but not with revisions 547-549 (the only revisions I have tested).
In fact, many features and optimizations have been added since 
xsltforms-1.0RC and a new release candidate version should be published 
soon.
>
> This has nothing to do with the namespaced attributes. It has nothing to do with elements versus attributes. Length also does not have anything to do with it.
Usually to fix bugs, the tiniest test case is the best way to locate the 
issue. Can you please send me one?
>
> By the way: what would be the version number of xsltforms-1.0RC (so I can test when the behaviour changed)?
xsltforms.js, line 45:     fileVersionNumber: 535,

Thanks!

-Alain