How did you manage that with incompatible DOM issues? Was it easier because of JS to manage that? Sounds like an entire file system resulted! :)
Chris Heilmann codepo8@toot.cafe
 @codepo8
22 Feb 2021
Replying to @mholzschlag
I already had to do app like functionality in the enterprise space, so writing out framesets in popup windows based on calculated information was common. Some of the JS had so many "parent." it felt like navigating a huge harddrive on console using "cd .."

Feb 22, 2021 · 10:32 AM UTC

3
2
Replying to @mholzschlag
Yes, of course you forked for each browser. Our often enough the project spec said IE only. But as an avid Netscape user I had none of that.
1
2
And of course the cardinal sin of "this site viewed in..." issues. I was NN as well, but <layer> was not spec'd much less semantically clear where "layer" meant so many things to the emerging disciplines (Photoshop, etc.) :)
1
2
more replies
Replying to @mholzschlag
God, I came to hate frame sets I frames anything with a frame. I was so glad as CSS developed
2
1
And absolutely hated right now really makes me sad. However the Cascade and a specific the algorithm could be created for many different uses. like I was thinking how complex Medical conditions could use specificity algorithms appropriately to get to build a widespread ontology.
1
Replying to @mholzschlag
I try to be compatible with everyone.
1
3