-
Notifications
You must be signed in to change notification settings - Fork 721
Support for iframe click events #12
Comments
Hi @jokerslab Could you give a little bit more context about the what you exactly mean with "populating the script with the appropriate frame selection". I'm open to new feature suggestions, I just need a bit more about what does it do and what the expect behaviour should be. |
If I have an html page with multiple iframes, and I start the recorder, no click events are captured from any of the elements in the iframe. I would expect the recorder to record events from all frames within the page. Additionally, when running puppeteer the click event has to be called on the frame where the selector/element parent document is. Thus I would imagine whenever capturing a click from an iframe, you would want to capture the name or id of the iframe so that when generating or running the script from the recorder you can call |
For example: |
Hi @tnolet |
I don't think that it was ever implemented. |
@crellison this functionality is implemented. Can you give me a clear, reproducable example so I can check for any bugs? Dealing with iframes is a bit of a pain, so there might be parts not covered in the code. |
@tnolet |
@chris2kus31 resolved is a bit tricky to define. I have working examples, but things might break in unexpected ways depending on timing and the actual DOM makeup. I will have a look at your example when I get the time. |
@tnolet If you look at my example from last year, you would see that it still doesn't work. |
Please contribute either a triage/analysis if what is going wrong or a fix for the bug if this is a high priority item for you.
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Raza <notifications@github.com>
Sent: Friday, April 12, 2019 11:33 AM
To: checkly/puppeteer-recorder
Cc: Tim Nolet; Mention
Subject: Re: [checkly/puppeteer-recorder] Support for iframe click events (#12)
@tnolet<https://github.com/tnolet> If you look at my example from last year, you would see that it still doesn't work.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#12 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ADoHKxktBMkp7eUXGoifPR9CE2swQMj9ks5vgFLSgaJpZM4WEhV2>.
|
@tnolet you are right. I'll look at it. My intention wasn't to demand this. |
I would love to see support for recording events from iframes and populating the script with the appropriate frame selection.
const frames = await page.frames(); const curFrame = frames.find(f => f.name() === 'activeFrame'); await curFrame.click('#selector')
The text was updated successfully, but these errors were encountered: