Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Sublocators using xpath locators not behaving the same as css locators

See original GitHub issue

Bug report

Node Version: 8.15.1
Protractor Version: 5.4.2
Angular Version: 1.5
Browser(s): Chromium
Operating System and Version macOS Mojave 10.14.6

Example DOM:

<html>
    <elementA>
    </elementA>

    <elementB>
        <elementA>
        </elementA>
    </elementB>
</html>

Behavior observed:

// these ones return both instances of "elementA" 
element(by.xpath('//elementB')).element(by.xpath('//elementA'));
element(by.xpath('//elementB')).all(by.xpath('//elementA'));

// these ones work as documented, only returning the "elementA" nested inside "elementB"
element(by.xpath('//elementB')).$('elementA');
element(by.xpath('//elementB')).$$('elementB');

Issue Analytics

State:
Created 4 years ago
Comments:5

Top GitHub Comments

1reaction

Jayasankar-mcommented, Jan 1, 2020

@costanza5813 can u try with .// foreg:

    element(by.xpath('//elementB')).element(by.xpath('.//elementA'));
    element(by.xpath('//elementB')).all(by.xpath('.//elementA'));

0reactions

Jayasankar-mcommented, Jan 12, 2020

@praveendvd You can directly use as $('ul').$('li')

It finds child anywhere under Ul not directly under . If the structure is like ul>span>il , still the locator finds the element . I need the equivalent of ./ Xpath

@praveendvd I don’t think CSS has a way to refer the current node like that