RCMaehl [Any]PlEaSe CeNtEr ThAt DiV
jiberishAs an amateur web designer in the 90s and early 2000s, this speaks to me. I stopped web development when CSS became popular and I couldn’t wrap my head around it.
Is there a petition I can sign to scrap all this nonsense modern web progress and go back to that beautiful, dial-up friendly HTML?
AcetamideLet’s just design every website using a table again. Or even better, frames!
I stand by that iframes had their place, even if the backend devs absolutely hated them.
They still have their place; for example to embed Google Maps or a YouTube video. Generally, whenever you want to embed something from a different website you have no control over, that shouldn’t inherit your style sheets, and should be sandboxed to prevent cross site scripting attacks.
Are iframes really sandboxed in different processes than the main frame? On which browsers?
Iframes may not necessarily run in a different process (although they do at least in Chrome and Firefox, if the iframe is from a different host than the main frame), but they have a different JavaScript execution context, and the iframe has no access to the main frame’s DOM or global variables. Also, you can restrict with the
sandbox attribute what the iframe should be allowed to do.
