5 ms·
It’s not like it’s difficult. This isn’t the world of IE6, where a bloated Netscape 4.7 which failed to work on many sites was the only alternative. (Kant remem
by midasuni 6y ago
It’s not like it’s difficult. This isn’t the world of IE6, where a bloated Netscape 4.7 which failed to work on many sites was the only alternative. (Kant remember when KHTML - later konqurer - became more usable than Phoenix/Firebird/Firefox)
- psychstudio 6y agoOh I loved Konq in the olden days. A single tabbed browser for both file system and web. Loved that thing. khtmlview was also an awesome browser component which I made use of in a few QT projects.
- nottorp 6y agoLet's remember that khtml was embraced by Apple and became (forked) the rendering engine in Safari...
- emayljames 6y agoI'd respectfully disagree, Netscape (Gecko) had better, more up to date standards. The issue was always folks not testing on other than Internet Exploder.
- Andrew_nenakhov 6y agoI actually found that the best way in that (horrible) era was to develop Opera-first. That way the amount of fixes for IE and Mozilla was much less than if choosing any of these two as firstm
- int_19h 6y agoIt didn't when Netscape 4 (which was pre-Gecko) was a thing. The IE vs NN browser war saw both adopting various incompatible non-standard features - e.g. layers in NN, innerHTML in IE - but the set that IE ended up with was closer to what was eventually standardized as HTML5/CSS/DOM.
- emayljames 6y agoThat sounds like a ruff time for devs.
- midasuni 6y agoBlink Problem was everyone had IE, websites were written for IE, activex, vbscript, etc If it worked in Netscape fine, but large numbers didn’t. On top of that, Netscape was a right resource hog.