ru.yandex.qatools.htmlelements.loader.decorator.HtmlElementDecorator error with custom ElementLocatorFactory

[emaks]

when I try to initialize page elements with custom ElementLocatorFactory, like

    public AbstractPage(final WebDriver driver) {
        this.driver = driver;
        PageFactory.initElements(new HtmlElementDecorator(new NotDefaultElementLocatorFactory(this.driver)), this);
    }

in private <T extends HtmlElement> T decorateHtmlElement(Class<T> elementClass, ClassLoader loader, ElementLocator locator, String elementName) { } function
when PageFactory.initElements(new HtmlElementDecorator(elementToWrap), htmlElementInstance); line is executed will be used default HtmlElementLocatorFactory class

[aik099]

Can you please link the code line you're talking about here?

[emaks]

here you are

[aik099]

In that line the HtmlElementDecorator is used, but that's ok because the locator factory you've given is still used. Isn't it?

[emaks]

no, instance of new HtmlElementDecorator(elementToWrap) will be initialized using

public HtmlElementDecorator(SearchContext searchContext) {
    this(new HtmlElementLocatorFactory(searchContext));
}

constructor where default ElementLocatorFactory is used

[emaks]

In that case, child elements will be initialized by using default(HtmlElementLocatorFactory) class. but, I expect them to be initialized by using class from parent(NotDefaultElementLocatorFactory)

[artkoshelev]

yep, i see now, that's a tricky piece... can you please share a problem you are trying to solve with custom ElementLocatorFactory? so i can write the test and propose solution? or you can write failing test describing your problem and pull request it.

[emaks]

I want to add possibility to change timeOutInSeconds parameter

[aik099]

If I remember correctly there was a task for making that value configurable on per-element basis.

[artkoshelev]

yep, here is abandoned PR #63, you can fix all the problems here and we'll merge it

[emaks]

please, see #82

[emaks]

@artkoshelev are there any updates in #82?

[artkoshelev]

@emaks will look at it in a few days, thank you

[andrew-sumner]

I was just about to raise an issue on this myself as have struck the same problem on work related to issue #56. Any idea when a new version might be released?