Threads Tapestry 5.3.8 vs 5.4.3

I've got an issue/question regarding threads in tapesty. We have application that is using tapestry. When we updated from 5.3.8 to 5.4.3 I've found that ajax request are not handled in separate thread. For example: I have a long process that was executed in controller/class. However, I've got als

Retrieving elements after a zone update changed their id.

Hi everybody, We are using Tapestry 5.4.3 (successfully migrated from 5.3.8, just for the record). I am writing Selenium tests for this webapp and I am having a problem related to the fact that after a zone update Tapestry changes the client id of the elements, like explained in detail under "