select1 with and without "appearanace" attribute

>
>
>
> I'm using a <select1> and have found the following:
>
>
>
> If it has no "appearance" attribute, the drop-down box that displays only
> allows selection of the first item in the list *after* selecting some other
> item in the list and then changing it. In other words, without the
> appearance attribute, you can't easily select the initial item in the list.
>
>
>
> However, if you put the "appearance" attribute on the <select1> (with any of
> the three allowed values) the problem disappears.
>
>
>
> Since the "appearance" attribute is optional, the behavior that I'm seeing
> when it's absent is clearly problematic. Any guess as to whether this is an
> XForm issue, or one of converting the XForm into HTML via OPS?
>
>
>
> 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
>
>
>

> XForm issue, or one of converting the XForm into HTML via OPS?
>
>
>
> Thanks,
>
>
>
> Don
>
> --
> You receive this message as a subscriber of the

> Hi Alex,
>
> See the attached file. The first item, when running in the sandbox,
> can't be selected to update the element <propertySelection>. The others
> can. You can only get the first item to select if you first pick another
> item, and then change to the first one.
>
> Thanks,
>
> Don
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of
> Alessandro Vernet
> Sent: Thursday, February 09, 2006 6:58 PM
> To: [hidden email]
> Subject: Re: [ops-users] select1 with and without "appearanace"
> attribute
>
> Hi Don,
>
> I can't reproduce the issue. I have tried to edit
> xforms-controls/view.xhtml and remove the appearance="full" on the
> first <xforms:select1>. It then appears as a combo box, the second
> value is selected (FedEx), and I can select the first value (UPS) in
> the browser just fine. Maybe there is something else in your code that
> triggers this behavior. Would you have some code shows the issue and
> runs in the sandbox?
>
> Alex
>
> On 2/8/06, Smith, Donald <[hidden email]> wrote:
> >
> >
> >
> > I'm using a <select1> and have found the following:
> >
> >
> >
> > If it has no "appearance" attribute, the drop-down box that displays
> only
> > allows selection of the first item in the list *after* selecting some
> other
> > item in the list and then changing it. In other words, without the
> > appearance attribute, you can't easily select the initial item in the
> list.
> >
> >
> >
> > However, if you put the "appearance" attribute on the <select1> (with
> any of
> > the three allowed values) the problem disappears.
> >
> >
> >
> > Since the "appearance" attribute is optional, the behavior that I'm
> seeing
> > when it's absent is clearly problematic. Any guess as to whether this
> is an
> > XForm issue, or one of converting the XForm into HTML via OPS?
> >
> >
> >
> > 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
>
>
>
>