Slashdot Mirror
KDE Gets Gecko/Mozilla Support
Sivar writes "Ars Technica reports that not only has the Gecko engine been ported to Konqueror, but the developers were able to finish the port in only four days during the week-long Akademy conference. With this port, Konqueror users now have a choice between two mature, powerful rendering engines."
It would be useful for testing web pages when you do not otherwise have access to a Windows machine, like me.
/usr/games/fortune
More choices, I see nothing negative in that.
The one thing I'd actually like to see in my GNOME environment is a KHTML based webbrowser, the html rendering feels much snappier than Gecko/Mozilla browsers.
There must be a reason why Apple desided to go with KHTML for their Safari browser instead of Gecko/Mozilla.
Can we have the rendering speed of KHTML (Konqueror's rendering engine) and the relatively-small memory footprint of Konqueror with the compatibility of Mozilla?
I mean, switching between rendering engines just to access a particular site sounds annoying. Almost as annoying as having to open an IE window for sites that don't work well w/ Mozilla or a Moz. window for sites that don't work in Konqueror...
Is Capitalism Good for the Poor?
"hasn't anyone ever tried to write a validated webpage that works in mozilla/firefox? it's nigh impossible, if you expect to use all of the features of html4.01 transitional or css1.0"
Smoke crack much? Writing validated HTML or XML pages in Mozilla is easy as hell. It's getting IE to render em right that is the hard part.
"have a look here: Mozilla's quirks mode. It's actually necessary to trick the browser into getting even somewhat close to standards compliant, and even then the formatting is all screwy by half."
I hope you were trying to be funny. Otherwise you could only be considered a retard. Actually read what the page says.
" Because existing content on the web is not standards-compliant or would appear in unintended ways on a standards-compliant browser, Mozilla handles some content in a backwards compatible way and some content according to standards.
There are three modes used by the layout engine: quirks mode, almost standards mode, and full standards mode. In Quirks mode, layout emulates nonstandard behavior in Navigator 4 and MSIE for Windows that is required not to break existing content on the Web. In full standards mode, the behavior is (hopefully) the behavior described by the HTML and CSS specifications. In almost standards mode, there are only a very small number of quirks implemented: those that break real pages on the web that use the DOCTYPEs that trigger almost standards mode."
Mozilla quirks mode is not about rendering pages in a standards compliant way. It is about rendering broken pages in broken ways to match the rendering of the worlds most popular broken browser Internet Explorer. Which has it's own quirks mode so as to be backwards compatable with it's own broken ancestors.
" No problems in ie 4, 5 or 6. no problems in Opera or with khtml. I have no trouble testing sandards-validated pages QNX browser, mac OS/X, netscape 4 or with any other damn browser. Just the unholy troika of moz-firebrid-netscape. I'm like, wtf?"
And after reading all that the rest of us are all like wtf was he smoking?
Mr. Gates, is that you?
Seriously, I'm a professional web designer. I build everything 100% XHTML and CSS standard; my designs usually work immediately without tweaking in Safari and Mozilla/Camino/Firefox. A good 25% of my time, however, is spent fixing the IE 5 and 6 bugs afterwards. That happens *every* time.
Maybe you're just trying to do some things the wrong way. It's possible to write code that is valid but still done the wrong way.