I made small refactoring in SeleniunUtils to make code more compact ant, I
believe, easier to read.
On Sat, Sep 14, 2013 at 1:50 PM, Maxim Solodovnik wrote:
> Hello Sebastian,
>
> It is great news :)
> We can make all (or almost all) ids constant :)
> According to Wicket documentation: "In case
Hi Maxim,
no we can't. The ids are generated by Wicket jQuery UI. For example the id
for the buttons in the forms. It will be a different id every time you
press f5 in the browser.
However with selenium you can write xpath selectors so that you don't need
to know what the id will be.
Sebastian
O
I thought we can call setMarkupId on any wicket component
I'll double check
On Sep 14, 2013 2:41 PM, "seba.wag...@gmail.com"
wrote:
> Hi Maxim,
>
> no we can't. The ids are generated by Wicket jQuery UI. For example the id
> for the buttons in the forms. It will be a different id every time
Not for the DialogButton
Those ids are pre generated. And I think wicket UI requires them to be that
way to make sure they are unique.
Sebastian
On Sep 14, 2013 7:44 PM, "Maxim Solodovnik" wrote:
> I thought we can call setMarkupId on any wicket component
> I'll double check
> On Sep 14, 20
Didn't know that :(
Maybe Sebastien will propose anything :) he usually answers same day :)
On Sep 14, 2013 2:56 PM, "seba.wag...@gmail.com"
wrote:
> Not for the DialogButton
> Those ids are pre generated. And I think wicket UI requires them to be that
> way to make sure they are unique.
>
> Seba
Hi Sebastian, i am currently on vacation. I am coming back to you end of
next week!..
Thanks & best regards,
Sebastien
On 13 sept. 2013, at 22:04, "seba.wag...@gmail.com"
wrote:
Hallo Sebastien,
I run into a couple of issues when tryting to use WicketTester to write
tests on classes and form
