ContentCenter Pro running in quirks mode

In light of a recent organizational upgrade to IE8, I've been doing some work with the various "compatibility modes" that are available in IE8. Depending on what page/site you're on, you can quite easily query what "mode" you are in by hitting F12.

Interestingly, I notice that all the Content Center Pro pages (we are running TS6.7.2 SP2) are running in 'quirks' mode.

From my understaning of 'quirks' mode, basically this means (in IE land at least) that IE8 is "pretending" to render in much the same manner as IE5.5! As far as I am aware, the reason it is running in 'quirks' mode is that the HTML isn't specifying a DOCTYPE, and the default behaviour for IE8 when no DOCTYPE is specified is to run in 'quirks' mode.

I am gob-smacked!

What this says to me is that the browser specification in the compatability matrix is largely insiginficant as it's alway going to run in 'quirks' mode.

Has anyone come across this before?

Have I got my thinking correct on this?

Find more posts tagged with

Comments

Adam Stoller

It doesn't really come as that much of a surprise to me - though it does explain why the UI doesn't render correctly in a number of browsers / browser versions. The HTML that the UI generates is often horrendous and trying to fix things via CSS is a royal pain because of the lack of using established standards - many of which, admittedly, took hold after the initial versions of TeamSite were produced.

I've often wished that they (Autonomy / Interwoven) took the time to fix the code that generates the UI - perhaps the next release which is supposed to have yet-another UI choice (besides CCPro and CCStd) will finally fix that - one can only hope....

Zamber

Hi, I'm coming from the future.

On 7.4.1 quirks mode still prevails. headers.inl (./iw-cc.war/base/util/headers.inl, ./iw-cc.war/teamsite/util/headers.inl, ./iw-wcmweb.ear/iw-dcf.war/base/util/headers.inl) have a part where if the user agent is IE then it adds <meta http-equiv="X-UA-Compatible" content="IE=5"/>.

In fact the decaltarion for it is splattered all around the place so it's pretty hard to change it.

The doctype declaration is also a factor here but from what I heard from my project lead they got it partially fixed in 7.4.1 (compared to v6).

One nasty consequence on IE8 and 9 of this is that in edit mode the web page edited is in quirks no matter the X-UA-Compatible declaration. This is a performance "feature" in IE as loading multiple versions of the rendering engine posed serious performance issues (as if it would not be slow already).

Rick Poulin

..and as a warning to any who might try this, lots of the UI (and especially sitepub) does not work at all in IE standards mode, even when you find a way to force it (I've been there).

As fish said, we're kinda stuck dealing with the quirks until HP rebuilds the UI to bring it up to date with current web standards.

Zamber

We dropped the idea. Even though it's possible, indeed it rains **** on some parts of the UI.