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 .."
3
2
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
Replying to @codepo8
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.) :)

Feb 22, 2021 · 10:38 AM UTC

1
2
Replying to @mholzschlag
Layer was like iframe. Under the hood any absolutely positioned DIV was treated by Netscape like a layer. It's interesting: back then 90% of issues was because of non transparency of the platform. No standard, no documentation. This manifested trial and error as a way to build.
1
2