sitespeedio / sitespeedio/sitespeed.io
Recording element timing events within iframes
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5k
- Forks
- 624
- Avg merge
- 4h 8m
- Merged PRs (30d)
- 2
Description
Your question
Hi, I'm trying to record element timings from within a nested iframe, about 3 levels down. This is due to how the application is written and will not change soon.
It also acts like a Single Page Application, requesting data and rendering dom elements after initial page load. To my understanding this means we cannot currently track visual metrics, hence trying to use element timing.
The elementtiming attributes are in place, and can be recorded without issue when running this one section standalone. However they are not picked up when fully in context.
I've tried running a long selector to trigger actions from the top context, and running commands.switch.toFrame() several times to get within the right context. In both cases, I can drive the behaviour I want, but the metrics are not reported.
Is there anything else I can try to get this? Thanks.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is identified in the issue. Start by reproducing the nested-iframe SPA case and inspect the element timing handling around repeated commands.switch.toFrame() calls; done means element timing metrics are reported from the nested iframe after dynamically rendered elements appear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100