Board Thread:Support Requests - Getting Technical/@comment--20130226214535/@comment-3335785-20130228011653

Dzylon wrote: Cåm wrote: Is a pure CSS tabber using  not viable currently? It wouln't have the issues of all the tabs loading like tabber does, doesn't rely on AJAX like tabview and is going to be far more customisable and easily accessed that header tabs. It's supported in ie9 and I noticed another blog mentioning ie8 support was being phased out. I'd say no. A lot of people are still using IE below version 9 (like 7%, last time I checked).

Edit - that said, an extension using IE conditionals to present a js version on unsupported browsers but a CSS-only version on the newer ones sounds like a good solution.

In Kirkburn's most recent blog, he mentions IE8 support will be dropped relatively soon: We plan to drop full support for IE8 in the near future. Released almost four years ago, it has now fallen far behind other browsers in many aspects. I assume there will be some measure of backwards compatibility, but dropping IE8 support allows things like moving the wiki-nav to CSS using  (an excellent example would be Pecoes' Wikimarks) reducing the possibility of the javascript having a small syntax error and breaking the entire thing. Sure, CSS can still have syntax errors, but unless someone renames the classes it should be more or less fine.

Maybe I'm a little javascript-wary, but if there's a pure CSS way of doing things I'll take it every time. It's much harder to 'turn off' CSS and I see far fewer CSS bugs on Wikia than I do javascript, and CSS errors can be far more blatant even if I can't see them in Chrome's console.