Web browser discussion: Make a new forum for Chrome?

[Japlabot]

Chrome is quite popular at the moment, there are lots of threads about it, and I think Chrome is here to stay.

[SVG Veteran]

Chrome's already got more users than Opera and Opera is here since forever.. I think its just cuz its Google

[:: Lyon ::]

Well that means we have to make a special forum for Chrome, Firefox, Safari, Opera, Internet Explorer.. not to mention other applications Adobe Photoshop, Microsoft Office, etc?

[Japlabot]

There already are special forums for Firefox, Safari, Opera and Internet Explorer.

[what]

Seeing as Chrome uses WebKit surely it'd make more sense just to modify the current WebKit forum to allow for Chrome-related topics?

[Fred Derf Veteran]

At least as a temporary measure, I have renamed the forum "KHTML & Webkit (Safari)" to "KHTML & Webkit (Safari/Chrome)":

https://www.neowin.net/forum/index.php?showforum=228

Edit:

I didn't like the inconsistency (some forums were named by the product while others were named by the engine) so I went and renamed them all.

-->Internet Explorer (Trident)

"Here you can discuss anything related to MSIE or the Trident layout engine"

-->Firefox (Gecko)

"Here you can discuss browsers, like Mozilla Firefox, that are based on the Gecko layout engine"

-->Opera (Presto)

"Here you can discuss anything related to the Opera Web Browser or the Presto layout engine"

-->Chrome/Safari (KHTML & Webkit)

"Here you can discuss anything related to browsers based on KHTML or the Webkit layout engines. This includes Google Chrome (Webkit), Apple Safari (Webkit) and KDE's Konqeror (KHTML)."

Edited September 5, 2008 by Fred Derf

[tom01]

I don't think so, atleast untill it's secure and stable but putting it in Webkit should be fine I guess.

[Japlabot]

Well done Fred. I noticed that too. Good job.

[tiagosilva29]

-->Chrome/Safari (KHTML & WebKit)

"Here you can discuss anything related to browsers based on KHTML or the WebKit layout engines. This includes Google Chrome (WebKit), Apple Safari (WebKit) and KDE's Konqueror (KHTML)."

Some little typos there... I also think that the example order should be the same as the layout order: set by time.

[Fred Derf Veteran]

I capitalized the "K" in WebKit and added the "u" to Konqueror

[Rob Veteran]

I believe that as of IE8 it's no longer 'Trident' - let me find the IE Blog post about this.

Hmm can't find it, I may be talking out of my ass.

[+Gary7 Subscriber²]

I still think that Browsers should not be a subsection but have their own section.

[Fred Derf Veteran]

I believe that as of IE8 it's no longer 'Trident' - let me find the IE Blog post about this.

Hmm can't find it, I may be talking out of my ass.

Trident version MSHTML.dll version Internet Explorer version Notes

Trident 4.0.x IE4 Initial trident version

Trident II 5.0.x IE5 improved CSS1.0 support and had sweeping changes in CSS2 rendering

Trident III 5.5.x IE5.5 corrected issues with CSS handling

Trident IV 6.0.x IE6 corrected the box model and added quirks mode with DTD switching

Trident V 7.0.x IE7 fixed many CSS rendering issues and added partial PNG alpha support

Trident VI 8.0.x IE8 first version to pass the Acid 2 test[1]

http://en.wikipedia.org/wiki/Trident_(layout_engine)