Hi, I 've not tested it personally but my client has used ff4 with my t5 application.
The unexpected result is that ff checks for that field to have a value... preventing tapestry own validation to execute. is that a kind of issue on tapestry?, I really don't know but maybe the required attribute is a new attribute from html5 or firefox propietary. well, perhaps some one has already experienced that and has developed some kind of workaround cheers. Nicolás.-
