Preventing context from passivate

Hello! In my Layout I have action/event links (logout, etc). If a page inside a layout passivates context, layout links get that context. But I don't want them to. How do you prevent links from getting page passivated context? Cheers, Adam

Re: Custom validator default error message

Hmm, I don't need a custom validator annotation. Example: I just created a class that extends AbstractValidator and contributed this to the FieldValidatorSource in my module: public class MaxBigDecimal extends AbstractValidator { private static final String

Re: Preventing context from passivate

I would expect action/event links to have page context as they are a part of the page where they live (for example a logout event link click, would cause tapestry to activate the containing page and then trigger the logout event handler on that page). Things like logout I would handle using a

Re: Custom validator default error message

Does this help? http://jumpstart.doublenegative.com.au/jumpstart7/examples/input/contributingvalidators Cheers, Geoff > On 1 Dec 2016, at 7:27 PM, Nathan Quirynen

Firefox: FormFragment hidden fields disabled

Hi, so today I found a weird bug: Firefox stores the disabled attribute of hidden formfragments between page reloads. It's the browser's autocomplete feature that can be turned off by adding the attribute autocomplete="off" to either form or input field. This behavior prevents form fields from

Custom validator default error message

Hi, I have a Tapestry module contributing some custom validator implementations. How can i set default validation error messages for these in Tapestry 5.4? In older Tapestry versions I think you had to contribute a message catalog to the ValidationMessagesSource service, but this does not