Re: Generated IDs

Hi, See MarkupSettings#setMarkupIdGenerator(). The default ids are not that random. For a given scenario that starts with a new session the ids will be the same. On Feb 6, 2017 6:27 PM, "Bas Gooren" wrote: You can always register a component instantiation listener (or on before

Re: Generated IDs

You can always register a component instantiation listener (or on before render listener etc) in development mode, and let it set markups ids in any way you want to provide stable ids. E.g. a configure listener, which listens for Page instances and runs a visitor over all it’s components to

Re: Generated IDs

Yes, but we have a whole lot of existing pages and fields and links and buttons. I was kind of hoping I could just get wicket's generated IDs to be stable from page run to page run, and avoid getting a work request approved to go back and tweak every field. -- View this message in context:

Re: Generated IDs

Hi, You can also set the html id directly if you don't need it to be automatically generated ie: div wicket:id="myId" id="myId" Hope this helps, Sebastien. On Mon, Feb 6, 2017 at 4:58 PM, Entropy wrote: > Our test team wants to run selenium scripts against our pages,

Generated IDs

Our test team wants to run selenium scripts against our pages, and wants stable IDs to go against. Wicket tends to generate random, and most annoyingly, inconsistent ones that change with each run of the page. Obviously, we can setMarkupId on every component manually, but I was wondering if