Bug 1066001

Summary:	W3C validator: Use of legacy HTML attributes not compliant with XHTML 1.0 Strict type document.
Product:	[JBoss] JBoss Enterprise Portal Platform 6	Reporter:	Lucas Ponce <lponce>
Component:	Portal	Assignee:	Lucas Ponce <lponce>
Status:	CLOSED UPSTREAM	QA Contact:	Tomas Kyjovsky <tkyjovsk>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	epp-bugs, ppalaga
Target Milestone:	DR02
Target Release:	6.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	JBoss Portal produced XHTML-type documents, in which some legacy HTML elements were not compatible in a XHTML 1.0 Strict document. This caused non-compliance issues with W3C XHTML validation. The non-compliant elements are fixed with a compliant XHTML workaround. Additionally, XHTML produced by JBoss Portal is modified from strict to transitional to prevent future conflicts for legacy elements in third party portlets.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-02-10 03:35:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1050065

Description Lucas Ponce 2014-02-17 13:36:50 UTC

Description of problem:

JBoss Portal 6.1.0 produces XHTML 1.0 Strict type documents.

There are some legacy html elements (i.e. target="_blank") not compatible with XHTML 1.0 Strict type document creating a non compliant markup.

Version-Release number of selected component (if applicable):

6.1.0

How reproducible:

Always

Steps to Reproduce:
1. Login into Portal.
2. Review source code generated.
3. Validate with http://validator.w3.org/ tool.

Actual results:

Pages with non compliant legacy html elements.

Expected results:

Pages without non compliant html elements making pass a w3c validation test.

Additional info:

Comment 2 Peter Palaga 2014-03-21 15:04:22 UTC

https://github.com/gatein/gatein-portal/pull/803 was merged in upstream.

Comment 3 Tomas Kyjovsky 2014-05-26 16:16:38 UTC

Looking at the source code of /classic/home in 6.2.0.ER2: there are still some target='_blank' occurences hidden inside exo webui JS.

onclick="this.target= '_blank';return true;"

Comment 4 Lucas Ponce 2014-05-26 16:20:10 UTC

Hi Tomas,

From a w3c validation perspective. Workaround to put target attribute inside "onclick" event is valid.

What is not valid is to add a "target" attribute in the xhtml element.

Comment 5 Tomas Kyjovsky 2014-05-26 16:46:49 UTC

I don't know, the workaround seems nasty. Putting it in JS is just avoiding the validation process which only checks the initial state of the doc. The user will eventually get a document that is ivalid against XHTML 1.0 Strict. Wouldn't it be better to declare XHTML 1.0 Transitional instead?

Comment 7 Red Hat Bugzilla 2025-02-10 03:35:06 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.