nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

upgrade from HTML 3.2 to higher version

Liyun_Li

Hi, the default doctype for html pages shipped with our cs10 is

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">

We want to upgrade to a higher version of HTML but failed on the first step. As soon as we change the default to

<!DOCTYPE html> or <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Final//EN">

we notice the core pages are not displayed correctly, looks like css files are not working properly. We are using IE8. Anyone has gone through this process and any suggestion? Thanks in advance!

Find more posts tagged with

Comments

Greg_Griffiths

As the Weblingo layer is set at 3.2, you would need to review all the HTML/CSS etc as part of the upgrade to ensure that you get correct rendering, this is likely to be better than using a Transition DocType.

Am a little suprised that OT are shipping CS10 with a HTML 3.2 UI, but as IE 8 will happily handle any valid HTML format and the bulk of the functionality is in the OScript layer, it is understandable that this is less of an issue for them.

Liyun_Li

Thanks for your reply, Greg.

I understand it is users' responsibility to review/update their own html pages to a higher version. But does Opentext provide any support on upgrade of the core pages, like livelink.css?

Greg_Griffiths

That's a question for OT, I'd ask either OT Support or your account manager as it may be in the product roadmap.

GregBrinker

I also am suprised at this. From a web developers POV, IE is a nightmare to begin with. Add on top of this that the HTML 3.2 Standard is from 1996. When this DOCTYPE is set it forces IE into 'Quirks' mode, which makes it almost impossible to write a customview with any kind of modern W3C standards.

I understand that Open Text is not too concerned about having 'validated' UI HTML, but DANG - Spend some time updaing your old, crappy code and CSS for the UI to a somewhat-modern standard. The HTML 4.01 DOCTYPE is at least an accepted standard that puts IE into a 'Standard' document mode instead of 'Quirks'.

Greg_Griffiths

Not speaking for OT, as they can speak for themselves , as a Development Manager, I am often asked to choose what people work on given finite resources, do I fix the bugs or make the UI HTML4 compliant when it is currently working ? bug fixing will usually win.

Additionally, there is also the lowest common denominator position, OT will have an idea of the oldest browser that is being used with their system, some large firms and governments are still using IE6 for example, so while it would be nice to update to HTML 5, why stop at 4 , most firms would have a lead time which would delay the issue. If these firms are your big customers then they may carry more weight in keeping them happy rather than if it was just a small 30 user place for example.

Just my thoughts, am sure OT will have an official answer, suggest you ask Support / Account Managers for it.

James_Storm

The issues and concerns regarding the doctype used in CS10's HTML is understood. As someone who dabbles in HTML myself, I do appreciate the benefits of the more recent HTML standards. Indeed, it is our intention to fully support, and take advantage of, HTML5 and the capabilities of HTML5-compliant user agents in the future.

However, we have the challenge of finding the balance between keeping up with standards and maintaining backward compatibility. There is a very large Content Server customer base and partner ecosystem that have built modules and customizations that depend on the way web browsers interpret Content Server's HTML. Therefore, making a big change to support contemporary and futuristic HTML coding techniques carries with it the risk of adversly affecting much work that has been done in the past.

So, we reserve making big changes like these for major releases of the product. With the release of CS10 two years ago, we decided to not focus on the HTML doctype but on other things like end user functionality, internationalization, server performance, and hardware usage efficiency. We will be considering updating the doctype in the next major version of Content Server. Watch the roadmap updates for timelines.

Regards,

James Storm

Content Server Product Management Director

Miroslav_Svoboda

Is the doctype on higher version in CS10.5?

David Templeton

It will be 3.2 until September, then 10.5 will be 4.01

Thanks
David

Sent from my mobile

From: eLink Entry: Content Server Development Forum

Sent: Friday, June 13, 2014 6:20 AM

To: eLink Recipient

Reply To: NTAyMzAwMDMA@elinkkc.opentext.com

Subject: upgrade from HTML 3.2 to higher version 2

upgrade from HTML 3.2 to higher version 2

Posted by miroslav.svoboda@unicornsystems.eu (Svoboda, Miroslav) On 06/13/2014 06:18 AM

Is the doctype on higher version in CS10.5?

[To post a comment, use the normal reply function]
Topic:	upgrade from HTML 3.2 to higher version
Forum:	Content Server Development Forum
Content Server:	Knowledge Center

David Templeton

The change to the higher doctype will only be on 10.5 September update. There is an impact on the rendering so it won’t be done for 10 and most things still work.

David

From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Friday, June 13, 2014 6:20 AM
To: eLink Recipient
Subject: upgrade from HTML 3.2 to higher version 2

upgrade from HTML 3.2 to higher version 2

Posted bymiroslav.svoboda@unicornsystems.eu (Svoboda, Miroslav) On 06/13/2014 06:18 AM

Is the doctype on higher version in CS10.5?

[To post a comment, use the normal reply function]
Topic:	upgrade from HTML 3.2 to higher version
Forum:	Content Server Development Forum
Content Server:	Knowledge Center