It's a bug if that's the case. I'd like all components to work under
any combination of situations people want so it'd be easy to qualify
it as a bug..
On 2/8/07, Jeremy F. Kassis <[EMAIL PROTECTED]> wrote:
I'm having the same problem. I looked into this once. It has something to do
with how the Dialog component works. It actually copies the DOM tree of the
elements within the Dialog into a DOM island that it stuffs under the window
or document object I think. So, basically, the Input element within your
form isn't the same input element that the autocompleter attached to. I may
look further at how to handle this, but it ain't trivial.
Here's what I'm thinking of...
Add a dojo listener to the show() method of the dialog that contains the
autocompleter.
Use tapestry.widget.synchronizeWidgetState("tagAutoCompleter", "Select",
tagAutoCompleter, true); to recreate the widget.
VitalyA wrote:
>
> Hi all,
> I use Tapestry 4.1.2 snapshot.
> Can I use together Dialog and Autocompleter components?
> I want to open Dialog which contains Autocompleter.
> Currently it doesn't work, Autocompleter rendered without options.
> Thanks in advance,
> Vitaly
>
--
View this message in context:
http://www.nabble.com/Autocompleter-and-Dialog-tf2879504.html#a8878447
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
