This is a good idea @JimScott ,
The main point I think though is that there are so many scenarios that a project can take that any and all methods of approach have merit depending on said scenarios.
We can use classes, ID, names, data attributes to solve issues that each throw up whether that be Layouts with similar elements for same use, Layouts with symbols and so on… We also can only use the name tag in a few situations.
For @JimScott’s approach,
One thing I would say is I always try and avoid editing within inner html on elements manually if I can. Just find it a pain in the arse and cannot clearly see what is going on. I personally would write a script to do it all for me or
would try and make the iFrame element a Persistent Symbol across scenes with one name. and use the button’s Actions inspector ‘On Mouse Click’ and ‘Go to Url’ to open a bookmarklet with the iframe as the target.
This is just to make editing easier and seeing what is what at a glance.