[Bug]: generateLocator depends on timing to not produce locators that violate strict mode about playwright HOT 2 CLOSED

I understand that it's not planned to address the timing issues on your side, but I would like to at least get some documentation about the fact that all locators ignore invisible elements completely.

To me it is also surprising that the following page

<div>
    <button
        name="senddata"
        style="display: none;"
        >
        <span>Agree to all</span>
    </button>
    <button
        name="senddata"
    >
        <span>Agree to all</span>
    </button>
</div>

The locator generator acts based on the current state of the page, it doesn't know if one of currently invisible elements will become visible or a new element matching same locator is going to be added by javascript later (or the order of elements may change etc.). If you know that the locator is not going to be unique, you can call the generator when the page is in appropriate state or you can always alternate the result to be more resilient to changes in the page.

Closing this issue as not planned.

from playwright.