3 ms·

Thanks for the follow up. So they handle the upstream collisions nicely (i.e. the embedded content not affecting the parent site). But the other side of it is

Thanks for the follow up. So they handle the upstream collisions nicely (i.e. the embedded content not affecting the parent site). But the other side of it is the downstream (i.e. the parent site doing `div { color: black }` which propogates to the embedded content) and it won't handle that nicely. You can do something like cleanslate does (https://github.com/premasagar/cleanslate https://github.com/premasagar/cleanslate) to aggressively unset so the parent sites CSS gets "disarmed". But it is not the smoothest and things like REM unit values still propagate to the embedded content.

SebastianKra 2y ago
Yeah you're right about that. I consider global styling of tags such a bad practice that I would suggest removing all of that immediately. I had to deal with this in a project using https://materializecss.com https://materializecss.com, and it was such an uphill battle to override these styles. Because apparently nobody considered that an application might have more than one kind of table https://materializecss.com/table.html https://materializecss.com/table.html.