New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Measure multiple element timing and page visual complete for a page with shadow DOM #4136
Comments
Hi @ovenger-snow can you provide an example page/URL, then I could try to add a fallback for the visual elements to get it from the shadow DOM? |
First example found - https://www.htmlelements.com/demos/menu/shadow-dom/index.htm P.S. After some research, found out that Element Timing API doesn't support shadow DOM. So seems like option 1 is not viable. |
What do you want to measure on that page? :) If you can share your real URL and exact what you want to measure it will be easier. For element timings: The Chrome API does not support I think as long as it's attached to the DOM and you can get the position, you can get it for the visual elements? It works like this: it finds the element, gets the position and then uses that position in the video recording and calculates when it was painted. Marks and stop watch can measure things but will not now when things is painted on the screen. |
I can't share the current app I am working on. I didn't dive deep into how element timing works. Happy to hear your thoughts on how you would do it. Currently, just evaluating different options. |
Your question
I am looking for some suggestions on how properly this can be done.
Goal: Execute tests against the application with shadow DOM and measure multiple elements/components timing + visual complete. So we would be able to get all the timings both when multiple elements are available and full page visual complete.
As of now, I can see several solutions to each but I assume there are even more.
--scriptInput.visualElements
. The limitation of it is that it doesn't work for shadow DOM as you can get it by singledocument.body.querySelector
. I understand that you may annotate elements but that will require additional work from dev teams.Including a sample of how I am doing it with stopWatch
The text was updated successfully, but these errors were encountered: