In light of the fact that it's getting pretty late where I am and I've not had a chance to actually clean-up any of the documentation/demo page content I think the beta-1 release will have to wait a day or two more.

On 12/4/05, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
Alright, the house of cards that was the MSIE submit button bug has been fixed. Don't play around with the submit link/button/fieldobserver/etc field names/id's unless you really know what's going on with everything ;) (MSIE can't attach event listeners to dom nodes with non-unique ID attributes, which is what happens to elements of type input that have both a hidden input field and a regular input field...)

test away, I haven't done anything besides this for the last few hours. I hope I can take my anger out on this small bag of M&M's.  ;)

jesse
On 12/4/05, Leonardo Quijano Vincenzi <[EMAIL PROTECTED]> wrote:
Jesse Kuhnert wrote:
> I'm getting closer...One nasty little bug in IE that still needs to be
> fixed.
>
> Yeah, we can wait for the RadioGroup, but just know that we'll be
> constrained to tapestry's 4.0.1 release to get it. (Well, we can use
> tapestry from subversion, but that sounds like trouble).
It sounds like trouble! At least while Tapestry is not stable. I still
have my suspicions about Tapestry's stability, even if you tag it as
"release-candidate". But well, time will tell!!

As for the uniquely referenceable DOM id on Tapestry elements, what I
think would work is a common component property that guarantees
uniqueness for *all* tapestry components. Like -clientId- I guess.

So, we could have a component property:

someComponent.getUniqueId();

And then we can use it in Tacos like this:

updateComponents="ognl:{components.someComponent.uniqueId}"

Right ?
We could even go beyond that by letting tacos process component bindings

updateComponents="component:{someComponent}"

(maybe that's not correct syntax... but it could be!")
We can always mix:

updateComponents="ognl:{components.someComponent, 'someNonTapestryID'}"

Those bindings are important if we want to make reusable Tacos components.

--
Ing. Leonardo Quijano Vincenzi
DTQ Software




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Tacos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tacos-devel


Reply via email to