Orbeon Forms community mailing list

initial item in itemset not selecting

Classic

List

Threaded

13 messages Options

Smith, Donald

initial item in itemset not selecting

I have this content in my model:

</set>

And am using this XForms to present it:

<xforms:select1 ref="propertySelection" >

<xforms:itemset nodeset="instance('main')/properties/set/property">

<xforms:label ref="@label"/>

<xforms:value ref="@id"/>

</xforms:itemset>

</xforms:select1>

Everything works fine, except the initial item in the set. If you try to select “release date”, it won’t select. If you select something else, it works fine, and then you can change and select “release date” and it then selects.

Anyone ever seen such behavior before and know what the cause is?

Thanks,

Don

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Erik Bruchez

Re: initial item in itemset not selecting

Administrator

Don,

The attached example, based on your snippets, works in the sandbox.
There must be more the what you sent in your example.

Do you happen to have relevant bindings in your model, that could make a
list item non-relevant?

-Erik

Smith, Donald wrote:

> I have this content in my model:
>
>
>
> <set domain="XMLEditor">
>
> <property id="releaseDate" datatype="date" label="release date"/>
>
> <property id="isCommercialApplication" datatype="boolean" label="is
> commercial application"/>
>
> <property id="isOpenSourceOrFreewareApplication" datatype="boolean"
> label="is open source or freeware application"/>
>
> <property id="basicLookAndFeel" label="basic look and feel"
> range="userInterface"/>
>
> </set>
>
>
>
> And am using this XForms to present it:
>
>
>
> <xforms:select1 ref="propertySelection" >
>
> <xforms:itemset nodeset="instance('main')/properties/set/property">
>
> <xforms:label ref="@label"/>
>
> <xforms:value ref="@id"/>
>
> </xforms:itemset>
>
> </xforms:select1>
>
>
>
> Everything works fine, except the initial item in the set. If you try to
> select “release date”, it won’t select. If you select something else, it
> works fine, and then you can change and select “release date” and it
> then selects.
>
>
>
> Anyone ever seen such behavior before and know what the cause is?
>
>
>
> Thanks,
>
>
>
> Don

test.xhtml (2K) Download Attachment

Smith, Donald

RE: initial item in itemset not selecting

In reply to this post by Smith, Donald

Erik,

Interesting. The sample document I sent (viewTEST.xhtml) does *not* work
in my sandbox (wrt being able to select the first item in the pick list,
until you select something else first and then change your choice). As
you'll see by the attached original file, the only differences are the
hardcoding of the input instance document content and the removal of two
comments.

Strange.

Don

-----Original Message-----
From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
Sent: Monday, February 13, 2006 9:50 AM
To: [hidden email]
Subject: Re: [ops-users] initial item in itemset not selecting

Don,

The attached example, based on your snippets, works in the sandbox.
There must be more the what you sent in your example.

Do you happen to have relevant bindings in your model, that could make a

list item non-relevant?

-Erik

Smith, Donald wrote:

to
> select "release date", it won't select. If you select something else,

> works fine, and then you can change and select "release date" and it
> then selects.
>
>
>
> Anyone ever seen such behavior before and know what the cause is?
>
>
>
> Thanks,
>
>
>
> Don

view.xhtml (4K) Download Attachment

Erik Bruchez

Re: initial item in itemset not selecting

Administrator

Don,

I don't think I ever saw that viewTEST.xhtml. But you are saying that
things work now?

-Erik

Smith, Donald wrote:

> Erik,
>
> Interesting. The sample document I sent (viewTEST.xhtml) does *not* work
> in my sandbox (wrt being able to select the first item in the pick list,
> until you select something else first and then change your choice). As
> you'll see by the attached original file, the only differences are the
> hardcoding of the input instance document content and the removal of two
> comments.
>
> Strange.
>
> Don
>
> -----Original Message-----
> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
> Sent: Monday, February 13, 2006 9:50 AM
> To: [hidden email]
> Subject: Re: [ops-users] initial item in itemset not selecting
>
> Don,
>
> The attached example, based on your snippets, works in the sandbox.
> There must be more the what you sent in your example.
>
> Do you happen to have relevant bindings in your model, that could make a
>
> list item non-relevant?
>
> -Erik
>
> Smith, Donald wrote:
>> I have this content in my model:
>>
>>
>>
>> <set domain="XMLEditor">
>>
>> <property id="releaseDate" datatype="date" label="release date"/>
>>
>> <property id="isCommercialApplication" datatype="boolean" label="is
>> commercial application"/>
>>
>> <property id="isOpenSourceOrFreewareApplication" datatype="boolean"
>> label="is open source or freeware application"/>
>>
>> <property id="basicLookAndFeel" label="basic look and feel"
>> range="userInterface"/>
>>
>> </set>
>>
>>
>>
>> And am using this XForms to present it:
>>
>>
>>
>> <xforms:select1 ref="propertySelection" >
>>
>> <xforms:itemset nodeset="instance('main')/properties/set/property">
>>
>> <xforms:label ref="@label"/>
>>
>> <xforms:value ref="@id"/>
>>
>> </xforms:itemset>
>>
>> </xforms:select1>
>>
>>
>>
>> Everything works fine, except the initial item in the set. If you try
> to
>> select "release date", it won't select. If you select something else,
> it
>> works fine, and then you can change and select "release date" and it
>> then selects.
>>
>>
>>
>> Anyone ever seen such behavior before and know what the cause is?
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Don
>
>
> ------------------------------------------------------------------------
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Alessandro Vernet

Re: initial item in itemset not selecting

Administrator

In reply to this post by Smith, Donald

Don,

What I see in your example is that <propertySelection/> which is bound
to the combo box is initially empty. "Empty" does not correspond to
any value in the combo box, so when you load the page the first item
in the combo box ("release date") is active by default. Now if you
open the combo box and select "release date", nothing happen, because
this is the value that was already selected before. If you want to
have "release date" in the instance, you have select something else
first, and then come back to "release date".

Is this the problem you are describing?

Alex

On 2/13/06, Smith, Donald <[hidden email]> wrote:

> Erik,
>
> Interesting. The sample document I sent (viewTEST.xhtml) does *not* work
> in my sandbox (wrt being able to select the first item in the pick list,
> until you select something else first and then change your choice). As
> you'll see by the attached original file, the only differences are the
> hardcoding of the input instance document content and the removal of two
> comments.
>
> Strange.
>
> Don
>
> -----Original Message-----
> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
> Sent: Monday, February 13, 2006 9:50 AM
> To: [hidden email]
> Subject: Re: [ops-users] initial item in itemset not selecting
>
> Don,
>
> The attached example, based on your snippets, works in the sandbox.
> There must be more the what you sent in your example.
>
> Do you happen to have relevant bindings in your model, that could make a
>
> list item non-relevant?
>
> -Erik
>
> Smith, Donald wrote:
> > I have this content in my model:
> >
> >
> >
> > <set domain="XMLEditor">
> >
> > <property id="releaseDate" datatype="date" label="release date"/>
> >
> > <property id="isCommercialApplication" datatype="boolean" label="is
> > commercial application"/>
> >
> > <property id="isOpenSourceOrFreewareApplication" datatype="boolean"
> > label="is open source or freeware application"/>
> >
> > <property id="basicLookAndFeel" label="basic look and feel"
> > range="userInterface"/>
> >
> > </set>
> >
> >
> >
> > And am using this XForms to present it:
> >
> >
> >
> > <xforms:select1 ref="propertySelection" >
> >
> > <xforms:itemset nodeset="instance('main')/properties/set/property">
> >
> > <xforms:label ref="@label"/>
> >
> > <xforms:value ref="@id"/>
> >
> > </xforms:itemset>
> >
> > </xforms:select1>
> >
> >
> >
> > Everything works fine, except the initial item in the set. If you try
> to
> > select "release date", it won't select. If you select something else,
> it
> > works fine, and then you can change and select "release date" and it
> > then selects.
> >
> >
> >
> > Anyone ever seen such behavior before and know what the cause is?
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Don
>
>
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
>
>

--
Blog (XML, Web apps, Open Source):
http://www.orbeon.com/blog/

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet

Smith, Donald

RE: initial item in itemset not selecting

In reply to this post by Smith, Donald

Alex,

Yes, that is the problem I'm describing. I take it that by the first
part of your answer is that one thing you could do is populate the
<propertySelection> element with the first item in the list as the page
is loaded, providing a default selection of the first item in the list:

<propertySelection>release date</propertySelection>

That's fine. But what if you *didn't* want an initial, default
selection, but want the first item in the list to be selectable without
having to choose something else first?

Thanks,

Don

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of
Alessandro Vernet
Sent: Tuesday, February 14, 2006 2:18 AM
To: [hidden email]
Subject: Re: [ops-users] initial item in itemset not selecting

Don,

What I see in your example is that <propertySelection/> which is bound
to the combo box is initially empty. "Empty" does not correspond to
any value in the combo box, so when you load the page the first item
in the combo box ("release date") is active by default. Now if you
open the combo box and select "release date", nothing happen, because
this is the value that was already selected before. If you want to
have "release date" in the instance, you have select something else
first, and then come back to "release date".

Is this the problem you are describing?

Alex

On 2/13/06, Smith, Donald <[hidden email]> wrote:
> Erik,
>
> Interesting. The sample document I sent (viewTEST.xhtml) does *not*
work
> in my sandbox (wrt being able to select the first item in the pick
list,
> until you select something else first and then change your choice). As
> you'll see by the attached original file, the only differences are the
> hardcoding of the input instance document content and the removal of
two
> comments.
>
> Strange.
>
> Don
>
> -----Original Message-----
> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
Bruchez

> Sent: Monday, February 13, 2006 9:50 AM
> To: [hidden email]
> Subject: Re: [ops-users] initial item in itemset not selecting
>
> Don,
>
> The attached example, based on your snippets, works in the sandbox.
> There must be more the what you sent in your example.
>
> Do you happen to have relevant bindings in your model, that could make

>
> list item non-relevant?
>
> -Erik
>
> Smith, Donald wrote:
> > I have this content in my model:
> >
> >
> >
> > <set domain="XMLEditor">
> >
> > <property id="releaseDate" datatype="date" label="release date"/>
> >
> > <property id="isCommercialApplication" datatype="boolean"

label="is
> > commercial application"/>
> >
> > <property id="isOpenSourceOrFreewareApplication"

datatype="boolean"

> > label="is open source or freeware application"/>
> >
> > <property id="basicLookAndFeel" label="basic look and feel"
> > range="userInterface"/>
> >
> > </set>
> >
> >
> >
> > And am using this XForms to present it:
> >
> >
> >
> > <xforms:select1 ref="propertySelection" >
> >
> > <xforms:itemset

nodeset="instance('main')/properties/set/property">

> >
> > <xforms:label ref="@label"/>
> >
> > <xforms:value ref="@id"/>
> >
> > </xforms:itemset>
> >
> > </xforms:select1>
> >
> >
> >
> > Everything works fine, except the initial item in the set. If you

try
> to
> > select "release date", it won't select. If you select something

else,

> it
> > works fine, and then you can change and select "release date" and it
> > then selects.
> >
> >
> >
> > Anyone ever seen such behavior before and know what the cause is?
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Don
>
>
>
>
> --
> You receive this message as a subscriber of the

[hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page:

http://www.objectweb.org/wws
>
>
>
>

--
Blog (XML, Web apps, Open Source):
http://www.orbeon.com/blog/

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Ryan Puddephatt

RE: initial item in itemset not selecting

Donald,
Probably best you add a blank item in like so:
<xforms:item>
<xforms:label>Please Select</xforms:label>
<xforms:value/>
</xforms:item>

This way it won't look as if the first item is selected in your list

Ryan Puddephatt
Software Engineer
TFX Group - IT UK
1 Michaelson Square
Livingston
West Lothian
Scotand
EH54 7DP

* [hidden email]
( 01506 407 110
7 01506 407 108

>-----Original Message-----
>From: Smith, Donald [mailto:[hidden email]]
>Sent: 14 February 2006 15:56
>To: [hidden email]
>Subject: RE: [ops-users] initial item in itemset not selecting
>
>Alex,
>
>Yes, that is the problem I'm describing. I take it that by the first
>part of your answer is that one thing you could do is populate the
><propertySelection> element with the first item in the list as the page
>is loaded, providing a default selection of the first item in the list:
>
><propertySelection>release date</propertySelection>
>
>That's fine. But what if you *didn't* want an initial, default
>selection, but want the first item in the list to be selectable without
>having to choose something else first?
>
>Thanks,
>
>Don
>
>-----Original Message-----
>From: [hidden email] [mailto:[hidden email]] On Behalf Of
>Alessandro Vernet
>Sent: Tuesday, February 14, 2006 2:18 AM
>To: [hidden email]
>Subject: Re: [ops-users] initial item in itemset not selecting
>
>Don,
>
>What I see in your example is that <propertySelection/> which is bound
>to the combo box is initially empty. "Empty" does not correspond to
>any value in the combo box, so when you load the page the first item
>in the combo box ("release date") is active by default. Now if you
>open the combo box and select "release date", nothing happen, because
>this is the value that was already selected before. If you want to
>have "release date" in the instance, you have select something else
>first, and then come back to "release date".
>
>Is this the problem you are describing?
>
>Alex
>
>On 2/13/06, Smith, Donald <[hidden email]> wrote:
>> Erik,
>>
>> Interesting. The sample document I sent (viewTEST.xhtml) does *not*
>work
>> in my sandbox (wrt being able to select the first item in the pick
>list,
>> until you select something else first and then change your choice). As
>> you'll see by the attached original file, the only differences are the
>> hardcoding of the input instance document content and the removal of
>two
>> comments.
>>
>> Strange.
>>
>> Don
>>
>> -----Original Message-----
>> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
>Bruchez
>> Sent: Monday, February 13, 2006 9:50 AM
>> To: [hidden email]
>> Subject: Re: [ops-users] initial item in itemset not selecting
>>
>> Don,
>>
>> The attached example, based on your snippets, works in the sandbox.
>> There must be more the what you sent in your example.
>>
>> Do you happen to have relevant bindings in your model, that could make
>a
>>
>> list item non-relevant?
>>
>> -Erik
>>
>> Smith, Donald wrote:
>> > I have this content in my model:
>> >
>> >
>> >
>> > <set domain="XMLEditor">
>> >
>> > <property id="releaseDate" datatype="date" label="release date"/>
>> >
>> > <property id="isCommercialApplication" datatype="boolean"
>label="is
>> > commercial application"/>
>> >
>> > <property id="isOpenSourceOrFreewareApplication"
>datatype="boolean"
>> > label="is open source or freeware application"/>
>> >
>> > <property id="basicLookAndFeel" label="basic look and feel"
>> > range="userInterface"/>
>> >
>> > </set>
>> >
>> >
>> >
>> > And am using this XForms to present it:
>> >
>> >
>> >
>> > <xforms:select1 ref="propertySelection" >
>> >
>> > <xforms:itemset
>nodeset="instance('main')/properties/set/property">
>> >
>> > <xforms:label ref="@label"/>
>> >
>> > <xforms:value ref="@id"/>
>> >
>> > </xforms:itemset>
>> >
>> > </xforms:select1>
>> >
>> >
>> >
>> > Everything works fine, except the initial item in the set. If you
>try
>> to
>> > select "release date", it won't select. If you select something
>else,
>> it
>> > works fine, and then you can change and select "release date" and it
>> > then selects.
>> >
>> >
>> >
>> > Anyone ever seen such behavior before and know what the cause is?
>> >
>> >
>> >
>> > Thanks,
>> >
>> >
>> >
>> > Don
>>
>>
>>
>>
>> --
>> You receive this message as a subscriber of the
>[hidden email] mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> ObjectWeb mailing lists service home page:
>http://www.objectweb.org/wws
>>
>>
>>
>>
>
>
>--
>Blog (XML, Web apps, Open Source):
>http://www.orbeon.com/blog/
>
>

Erik Bruchez

Re: initial item in itemset not selecting

Administrator

In reply to this post by Smith, Donald

Don,

I guess you are hitting this bug:

http://forge.objectweb.org/tracker/index.php?func=detail&aid=304287&group_id=168&atid=350207

The rationale would be that is the user does see a single selection list
(dropdown) with the first item selected, then that selection is expected
to be stored into the instance in case the current value of the, even if
the user does not actually touch the control.

I am not sure if that is all there is in your second paragraph.

-Erik

Smith, Donald wrote:

> Alex,
>
> Yes, that is the problem I'm describing. I take it that by the first
> part of your answer is that one thing you could do is populate the
> <propertySelection> element with the first item in the list as the page
> is loaded, providing a default selection of the first item in the list:
>
> <propertySelection>release date</propertySelection>
>
> That's fine. But what if you *didn't* want an initial, default
> selection, but want the first item in the list to be selectable without
> having to choose something else first?
>
> Thanks,
>
> Don
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of
> Alessandro Vernet
> Sent: Tuesday, February 14, 2006 2:18 AM
> To: [hidden email]
> Subject: Re: [ops-users] initial item in itemset not selecting
>
> Don,
>
> What I see in your example is that <propertySelection/> which is bound
> to the combo box is initially empty. "Empty" does not correspond to
> any value in the combo box, so when you load the page the first item
> in the combo box ("release date") is active by default. Now if you
> open the combo box and select "release date", nothing happen, because
> this is the value that was already selected before. If you want to
> have "release date" in the instance, you have select something else
> first, and then come back to "release date".
>
> Is this the problem you are describing?
>
> Alex
>
> On 2/13/06, Smith, Donald <[hidden email]> wrote:
>> Erik,
>>
>> Interesting. The sample document I sent (viewTEST.xhtml) does *not*
> work
>> in my sandbox (wrt being able to select the first item in the pick
> list,
>> until you select something else first and then change your choice). As
>> you'll see by the attached original file, the only differences are the
>> hardcoding of the input instance document content and the removal of
> two
>> comments.
>>
>> Strange.
>>
>> Don
>>
>> -----Original Message-----
>> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
> Bruchez
>> Sent: Monday, February 13, 2006 9:50 AM
>> To: [hidden email]
>> Subject: Re: [ops-users] initial item in itemset not selecting
>>
>> Don,
>>
>> The attached example, based on your snippets, works in the sandbox.
>> There must be more the what you sent in your example.
>>
>> Do you happen to have relevant bindings in your model, that could make
> a
>> list item non-relevant?
>>
>> -Erik
>>
>> Smith, Donald wrote:
>>> I have this content in my model:
>>>
>>>
>>>
>>> <set domain="XMLEditor">
>>>
>>> <property id="releaseDate" datatype="date" label="release date"/>
>>>
>>> <property id="isCommercialApplication" datatype="boolean"
> label="is
>>> commercial application"/>
>>>
>>> <property id="isOpenSourceOrFreewareApplication"
> datatype="boolean"
>>> label="is open source or freeware application"/>
>>>
>>> <property id="basicLookAndFeel" label="basic look and feel"
>>> range="userInterface"/>
>>>
>>> </set>
>>>
>>>
>>>
>>> And am using this XForms to present it:
>>>
>>>
>>>
>>> <xforms:select1 ref="propertySelection" >
>>>
>>> <xforms:itemset
> nodeset="instance('main')/properties/set/property">
>>> <xforms:label ref="@label"/>
>>>
>>> <xforms:value ref="@id"/>
>>>
>>> </xforms:itemset>
>>>
>>> </xforms:select1>
>>>
>>>
>>>
>>> Everything works fine, except the initial item in the set. If you
> try
>> to
>>> select "release date", it won't select. If you select something
> else,
>> it
>>> works fine, and then you can change and select "release date" and it
>>> then selects.
>>>
>>>
>>>
>>> Anyone ever seen such behavior before and know what the cause is?
>>>
>>>
>>>
>>> Thanks,
>>>
>>>
>>>
>>> Don
>>
>>
>>
>> --
>> You receive this message as a subscriber of the
> [hidden email] mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> ObjectWeb mailing lists service home page:
> http://www.objectweb.org/wws
>>
>>
>>
>
>
> --
> Blog (XML, Web apps, Open Source):
> http://www.orbeon.com/blog/
>
>
>
>
>
> ------------------------------------------------------------------------
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Smith, Donald

RE: initial item in itemset not selecting

In reply to this post by Smith, Donald

Yes, I think the bug report is the same issue.

Perhaps I can restate what I'm trying to accomplish more clearly:

I want the select items in the list to be bound to an empty node
(initially), so that if the user makes no selection, then the value of
the bounded node is, in fact, nothing. The problem is if the user makes
a selection, and selects the first item in the list, it doesn't get
selected. The only way to select it is to select some other item in the
list first and then return to the first item and select it.

I could, as Ryan suggested, put something like "Select item" as the
first thing in the list, but this seems like needless clutter in the
form and offensive from the point of view of the user.

Thanks for your help.

Don

-----Original Message-----
From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
Sent: Tuesday, February 14, 2006 11:56 AM
To: [hidden email]
Subject: Re: [ops-users] initial item in itemset not selecting

Don,

I guess you are hitting this bug:

http://forge.objectweb.org/tracker/index.php?func=detail&aid=304287&grou
p_id=168&atid=350207

The rationale would be that is the user does see a single selection list

(dropdown) with the first item selected, then that selection is expected

to be stored into the instance in case the current value of the, even if

the user does not actually touch the control.

I am not sure if that is all there is in your second paragraph.

-Erik

Smith, Donald wrote:
> Alex,
>
> Yes, that is the problem I'm describing. I take it that by the first
> part of your answer is that one thing you could do is populate the
> <propertySelection> element with the first item in the list as the
page
> is loaded, providing a default selection of the first item in the
list:
>
> <propertySelection>release date</propertySelection>
>
> That's fine. But what if you *didn't* want an initial, default
> selection, but want the first item in the list to be selectable
without

> having to choose something else first?
>
> Thanks,
>
> Don
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of
> Alessandro Vernet
> Sent: Tuesday, February 14, 2006 2:18 AM
> To: [hidden email]
> Subject: Re: [ops-users] initial item in itemset not selecting
>
> Don,
>
> What I see in your example is that <propertySelection/> which is bound
> to the combo box is initially empty. "Empty" does not correspond to
> any value in the combo box, so when you load the page the first item
> in the combo box ("release date") is active by default. Now if you
> open the combo box and select "release date", nothing happen, because
> this is the value that was already selected before. If you want to
> have "release date" in the instance, you have select something else
> first, and then come back to "release date".
>
> Is this the problem you are describing?
>
> Alex
>
> On 2/13/06, Smith, Donald <[hidden email]> wrote:
>> Erik,
>>
>> Interesting. The sample document I sent (viewTEST.xhtml) does *not*
> work
>> in my sandbox (wrt being able to select the first item in the pick
> list,
>> until you select something else first and then change your choice).

As
>> you'll see by the attached original file, the only differences are

the

>> hardcoding of the input instance document content and the removal of
> two
>> comments.
>>
>> Strange.
>>
>> Don
>>
>> -----Original Message-----
>> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
> Bruchez
>> Sent: Monday, February 13, 2006 9:50 AM
>> To: [hidden email]
>> Subject: Re: [ops-users] initial item in itemset not selecting
>>
>> Don,
>>
>> The attached example, based on your snippets, works in the sandbox.
>> There must be more the what you sent in your example.
>>
>> Do you happen to have relevant bindings in your model, that could

make

> a
>> list item non-relevant?
>>
>> -Erik
>>
>> Smith, Donald wrote:
>>> I have this content in my model:
>>>
>>>
>>>
>>> <set domain="XMLEditor">
>>>
>>> <property id="releaseDate" datatype="date" label="release date"/>
>>>
>>> <property id="isCommercialApplication" datatype="boolean"
> label="is
>>> commercial application"/>
>>>
>>> <property id="isOpenSourceOrFreewareApplication"
> datatype="boolean"
>>> label="is open source or freeware application"/>
>>>
>>> <property id="basicLookAndFeel" label="basic look and feel"
>>> range="userInterface"/>
>>>
>>> </set>
>>>
>>>
>>>
>>> And am using this XForms to present it:
>>>
>>>
>>>
>>> <xforms:select1 ref="propertySelection" >
>>>
>>> <xforms:itemset
> nodeset="instance('main')/properties/set/property">
>>> <xforms:label ref="@label"/>
>>>
>>> <xforms:value ref="@id"/>
>>>
>>> </xforms:itemset>
>>>
>>> </xforms:select1>
>>>
>>>
>>>
>>> Everything works fine, except the initial item in the set. If you
> try
>> to
>>> select "release date", it won't select. If you select something
> else,
>> it
>>> works fine, and then you can change and select "release date" and it
>>> then selects.
>>>
>>>
>>>
>>> Anyone ever seen such behavior before and know what the cause is?
>>>
>>>
>>>
>>> Thanks,
>>>
>>>
>>>
>>> Don
>>
>>
>>
>> --
>> You receive this message as a subscriber of the
> [hidden email] mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> ObjectWeb mailing lists service home page:
> http://www.objectweb.org/wws
>>
>>
>>
>
>
> --
> Blog (XML, Web apps, Open Source):
> http://www.orbeon.com/blog/
>
>
>
>
>
>

------------------------------------------------------------------------
>
>
> --
> You receive this message as a subscriber of the

[hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page:
http://www.objectweb.org/wws

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Erik Bruchez

Re: initial item in itemset not selecting

Administrator

Smith, Donald wrote:
> Yes, I think the bug report is the same issue.
>
> Perhaps I can restate what I'm trying to accomplish more clearly:
>
> I want the select items in the list to be bound to an empty node
> (initially), so that if the user makes no selection, then the value
> of the bounded node is, in fact, nothing. The problem is if the user
> makes a selection, and selects the first item in the list, it
> doesn't get selected.

I think your attempt to clarify has just failed with this sentence ;-)

> The only way to select it is to select some other item in the list
> first and then return to the first item and select it.
>
> I could, as Ryan suggested, put something like "Select item" as the
> first thing in the list, but this seems like needless clutter in the
> form and offensive from the point of view of the user.

So are we talking about the bug mentioned, or not? If so, good, I
understand the issue. But somehow your description above makes it
sound like it is not the same issue.

-Erik

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Ryan Puddephatt

RE: initial item in itemset not selecting

In reply to this post by Smith, Donald

Donald,
If you wanted an empty node, you could leave the label and value
empty, that way the first node would be selected, but it would be the empty
one. Allowing your user to select one from the list if they require.

Ryan Puddephatt
Software Engineer
TFX Group - IT UK
1 Michaelson Square
Livingston
West Lothian
Scotand
EH54 7DP

* [hidden email]
( 01506 407 110
7 01506 407 108

>-----Original Message-----
>From: Smith, Donald [mailto:[hidden email]]
>Sent: 14 February 2006 18:28
>To: [hidden email]
>Subject: RE: [ops-users] initial item in itemset not selecting
>
>Yes, I think the bug report is the same issue.
>
>Perhaps I can restate what I'm trying to accomplish more clearly:
>
>I want the select items in the list to be bound to an empty node
>(initially), so that if the user makes no selection, then the value of
>the bounded node is, in fact, nothing. The problem is if the user makes
>a selection, and selects the first item in the list, it doesn't get
>selected. The only way to select it is to select some other item in the
>list first and then return to the first item and select it.
>
>I could, as Ryan suggested, put something like "Select item" as the
>first thing in the list, but this seems like needless clutter in the
>form and offensive from the point of view of the user.
>
>Thanks for your help.
>
>Don
>
>-----Original Message-----
>From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
>Sent: Tuesday, February 14, 2006 11:56 AM
>To: [hidden email]
>Subject: Re: [ops-users] initial item in itemset not selecting
>
>Don,
>
>I guess you are hitting this bug:
>
>http://forge.objectweb.org/tracker/index.php?func=detail&aid=304287&grou
>p_id=168&atid=350207
>
>The rationale would be that is the user does see a single selection list
>
>(dropdown) with the first item selected, then that selection is expected
>
>to be stored into the instance in case the current value of the, even if
>
>the user does not actually touch the control.
>
>I am not sure if that is all there is in your second paragraph.
>
>-Erik
>
>Smith, Donald wrote:
>> Alex,
>>
>> Yes, that is the problem I'm describing. I take it that by the first
>> part of your answer is that one thing you could do is populate the
>> <propertySelection> element with the first item in the list as the
>page
>> is loaded, providing a default selection of the first item in the
>list:
>>
>> <propertySelection>release date</propertySelection>
>>
>> That's fine. But what if you *didn't* want an initial, default
>> selection, but want the first item in the list to be selectable
>without
>> having to choose something else first?
>>
>> Thanks,
>>
>> Don
>>
>> -----Original Message-----
>> From: [hidden email] [mailto:[hidden email]] On Behalf Of
>> Alessandro Vernet
>> Sent: Tuesday, February 14, 2006 2:18 AM
>> To: [hidden email]
>> Subject: Re: [ops-users] initial item in itemset not selecting
>>
>> Don,
>>
>> What I see in your example is that <propertySelection/> which is bound
>> to the combo box is initially empty. "Empty" does not correspond to
>> any value in the combo box, so when you load the page the first item
>> in the combo box ("release date") is active by default. Now if you
>> open the combo box and select "release date", nothing happen, because
>> this is the value that was already selected before. If you want to
>> have "release date" in the instance, you have select something else
>> first, and then come back to "release date".
>>
>> Is this the problem you are describing?
>>
>> Alex
>>
>> On 2/13/06, Smith, Donald <[hidden email]> wrote:
>>> Erik,
>>>
>>> Interesting. The sample document I sent (viewTEST.xhtml) does *not*
>> work
>>> in my sandbox (wrt being able to select the first item in the pick
>> list,
>>> until you select something else first and then change your choice).
>As
>>> you'll see by the attached original file, the only differences are
>the
>>> hardcoding of the input instance document content and the removal of
>> two
>>> comments.
>>>
>>> Strange.
>>>
>>> Don
>>>
>>> -----Original Message-----
>>> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
>> Bruchez
>>> Sent: Monday, February 13, 2006 9:50 AM
>>> To: [hidden email]
>>> Subject: Re: [ops-users] initial item in itemset not selecting
>>>
>>> Don,
>>>
>>> The attached example, based on your snippets, works in the sandbox.
>>> There must be more the what you sent in your example.
>>>
>>> Do you happen to have relevant bindings in your model, that could
>make
>> a
>>> list item non-relevant?
>>>
>>> -Erik
>>>
>>> Smith, Donald wrote:
>>>> I have this content in my model:
>>>>
>>>>
>>>>
>>>> <set domain="XMLEditor">
>>>>
>>>> <property id="releaseDate" datatype="date" label="release date"/>
>>>>
>>>> <property id="isCommercialApplication" datatype="boolean"
>> label="is
>>>> commercial application"/>
>>>>
>>>> <property id="isOpenSourceOrFreewareApplication"
>> datatype="boolean"
>>>> label="is open source or freeware application"/>
>>>>
>>>> <property id="basicLookAndFeel" label="basic look and feel"
>>>> range="userInterface"/>
>>>>
>>>> </set>
>>>>
>>>>
>>>>
>>>> And am using this XForms to present it:
>>>>
>>>>
>>>>
>>>> <xforms:select1 ref="propertySelection" >
>>>>
>>>> <xforms:itemset
>> nodeset="instance('main')/properties/set/property">
>>>> <xforms:label ref="@label"/>
>>>>
>>>> <xforms:value ref="@id"/>
>>>>
>>>> </xforms:itemset>
>>>>
>>>> </xforms:select1>
>>>>
>>>>
>>>>
>>>> Everything works fine, except the initial item in the set. If you
>> try
>>> to
>>>> select "release date", it won't select. If you select something
>> else,
>>> it
>>>> works fine, and then you can change and select "release date" and it
>>>> then selects.
>>>>
>>>>
>>>>
>>>> Anyone ever seen such behavior before and know what the cause is?
>>>>
>>>>
>>>>
>>>> Thanks,
>>>>
>>>>
>>>>
>>>> Don
>>>
>>>
>>>
>>> --
>>> You receive this message as a subscriber of the
>> [hidden email] mailing list.
>>> To unsubscribe: mailto:[hidden email]
>>> For general help: mailto:[hidden email]?subject=help
>>> ObjectWeb mailing lists service home page:
>> http://www.objectweb.org/wws
>>>
>>>
>>>
>>
>>
>> --
>> Blog (XML, Web apps, Open Source):
>> http://www.orbeon.com/blog/
>>
>>
>>
>>
>>
>>
>------------------------------------------------------------------------
>>
>>
>> --
>> You receive this message as a subscriber of the
>[hidden email] mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> ObjectWeb mailing lists service home page:
>http://www.objectweb.org/wws
>
>
>

Adrian Baker-2

Re: initial item in itemset not selecting

In reply to this post by Erik Bruchez

I'm not sure this is a bug - according to the spec:

(8.1.11 select1)
"For closed selections: If the initial instance value matches the
storage value of one of the given items, that item is selected. If there
is no match, the form control must indicate an out-of-range condition."

So, I would read this as saying that if the initial value is empty, and
there is no empty item in the itemset, then the control should be
flagged as invalid (forcing a choice from the user), rather than any
automatic selection being made. Although perhaps if required evaluates
to false for the bind, perhaps this means an empty node is acceptable
even if there is not an empty item in the itemset? Either way, in both
cases there wouldn't be any automatic change.

If you want to default a value you can do this by populating the
instance data or with an event on startup. There are lots of scenarios
where it's not acceptable or safe to default to the first choice in a
set of options - rather the form must enforce that the selection be
explicitly made by the user.

Adrian

Erik Bruchez wrote:

> Don,
>
> I guess you are hitting this bug:
>
> http://forge.objectweb.org/tracker/index.php?func=detail&aid=304287&group_id=168&atid=350207
>
>
> The rationale would be that is the user does see a single selection
> list (dropdown) with the first item selected, then that selection is
> expected to be stored into the instance in case the current value of
> the, even if the user does not actually touch the control.
>
> I am not sure if that is all there is in your second paragraph.
>
> -Erik

Erik Bruchez

Re: initial item in itemset not selecting

Administrator

Interesting point.

Except if the value is valid in the instance (i.e., there is no
constraint on the value to be empty, say), and the control is marked as
out of range, this probably does not impact validity at all. The control
is out of range, that's all. The user will still be able to submit his form.

As a solution, the XForms engine could:

o produces artificially a "Please select..." entry in the menu (if it's
a menu), and ideally marks the control with a certain class that allows
styling the control differently in this case.

o Once the user selects an entry in the menu, the "Please select..."
option disappaers.

o For apperances such as radio buttons, simply none of the radio button
is selected.

-Erik

Adrian Baker wrote:

> I'm not sure this is a bug - according to the spec:
>
> (8.1.11 select1)
> "For closed selections: If the initial instance value matches the
> storage value of one of the given items, that item is selected. If there
> is no match, the form control must indicate an out-of-range condition."
>
> So, I would read this as saying that if the initial value is empty, and
> there is no empty item in the itemset, then the control should be
> flagged as invalid (forcing a choice from the user), rather than any
> automatic selection being made. Although perhaps if required evaluates
> to false for the bind, perhaps this means an empty node is acceptable
> even if there is not an empty item in the itemset? Either way, in both
> cases there wouldn't be any automatic change.
>
> If you want to default a value you can do this by populating the
> instance data or with an event on startup. There are lots of scenarios
> where it's not acceptable or safe to default to the first choice in a
> set of options - rather the form must enforce that the selection be
> explicitly made by the user.
>
> Adrian
>
> Erik Bruchez wrote:
>> Don,
>>
>> I guess you are hitting this bug:
>>
>> http://forge.objectweb.org/tracker/index.php?func=detail&aid=304287&group_id=168&atid=350207
>>
>>
>> The rationale would be that is the user does see a single selection
>> list (dropdown) with the first item selected, then that selection is
>> expected to be stored into the instance in case the current value of
>> the, even if the user does not actually touch the control.
>>
>> I am not sure if that is all there is in your second paragraph.
>>
>> -Erik
>
>
>
> ------------------------------------------------------------------------
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws