Click with openPageTreePath without success in small width

[ayacoo]

Given is a very simple suite. One root page and one sub page. This is also visible in the normal backend via a browser.

The following screenshots.json is created for me

{
    "suites": {
        "CustomExtension": {
			"screenshots": {
				"_default": [
					{"action": "resizeWindow", "width": 1920, "height": 1080}
				],
				"BackendRootPage": [
					{"action": "see", "text": "Page"},
					{"action": "click", "link": "Page"},
					{"action": "makeScreenshotOfFullPage", "fileName": "BackendRootPage"}
				],
				"BackendRootPageContentElement": [
					{"action": "see", "text": "Page"},
					{"action": "click", "link": "Page"},
					{"action": "openPageTreePath", "path": ["Root"]},
					{"action": "makeScreenshotOfFullPage", "fileName": "BackendRootPageContentElement"}
				]
			}
        }
    }
}

I get the following error message with make-screenshots:

  [Facebook\WebDriver\Exception\ElementClickInterceptedException] element click intercepted: Element \<path class="chevron collapsed" d="M 4 3 L 13 8 L 4 13 Z" transform=" rotate(0)" style="fill: rgb(142, 142, 142);">\</path> is not clickable at point (264, 155). Other element would receive the click: \<div class="scaffold-content-overlay t3js-scaffold-content-overlay">\</div>
  (Session info: headless chrome=95.0.4638.69)                                                                                                                                                                                                                                                                                                    

Scenario Steps:

10. $I->openPageTreePath(["Root"])
 9. $I->click("Page",null)
 8. $I->see("Page",null)

In the first screenshot you can also see the reason quite well. An 800 width is used and the page tree is darkened. Trigger is the class scaffold-content-overlay t3js-scaffold-content-overlay

@media (min-width: 992px)
.scaffold-modulemenu-expanded .scaffold-content-overlay {
    display: none;
}

This class is treated differently again from 992px. I am unsure what to do here. Looks to me more like a bug in TYPO3, but maybe you can define the default width here in this tool without having to do that yourself in the screenshots.json?

And now I hope that I have been understood :-D

[linawolf]

That is the mobile view of the backend. You can either minimize the module menu or use a larger resolution. It isn't really a bug. if you click once in the overlay area the module menu is minimized and you can then access the page tree and or content area. Its just that using this tool you have to do the same...

[ayacoo]

OK no problem. You just have to define it :-) How can we prevent people from running into this. There would be a little info in the documentation super. So to speak a "Know Issues" or "FAQ" section. What do you think about this?

[linawolf]

Feel free to add one and make a PR ;)

[ayacoo]

Okay, I'll take care of it ;-)

[linawolf]

wonderfull

[DavidBruchmann]

@ayacoo if you still plan to work on it, it would be much appreciated, perhaps also in combination with #238.
I think it would be enough to improve the README, even a whole Documentation structure could be a longer term target.
In any case a short feedback is welcome if you still plan to do it.
Thanks anyway!