Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1065991 - W3C validator: Use of custom attributes for portal navigation portlets.
W3C validator: Use of custom attributes for portal navigation portlets.
Status: VERIFIED
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: Portal (Show other bugs)
6.1.0
Unspecified Unspecified
unspecified Severity unspecified
: ER01
: 6.2.0
Assigned To: Lucas Ponce
Tomas Kyjovsky
:
Depends On:
Blocks: 1050065
  Show dependency tree / graph
 
Reported: 2014-02-17 08:12 EST by Lucas Ponce
Modified: 2014-07-29 21:54 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
JBoss Portal produced XHTML-type documents, some of which implemented custom attributes that were valid for browsers but non-compliant with W3C specifications. The custom attributes are fixed by applying compliance work-arounds in the XHTML mark-up. JBoss Portal now renders custom attributes according to W3C XHTML validation rules.
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker GTNPORTAL-3406 Major Resolved Avoid the use of custom attributes for portal navigation portlets. 2015-07-31 16:02:21 EDT

  None (edit)
Description Lucas Ponce 2014-02-17 08:12:50 EST 
Description of problem:

JBoss Portal 6.1.0 produces XHTML 1.0 Strict type documents.

For a w3c validation, standard html elements can not contain custom attributes.

There are several custom attributes like "exo:getNodeURL", "exo:minWidth", "exo:minHeight" used creating 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:

Portal logged pages use these custom attributes not compliant with XHTML 1.0 Strict type document spec.

Expected results:

Portal pages without use of custom attributes making pass a w3c validation test.

Additional info:
Comment 2 Peter Palaga 2014-03-21 11:02:09 EDT 
https://github.com/gatein/gatein-portal/pull/803 was merged in upstream.
Comment 3 Tomas Kyjovsky 2014-05-26 12:11:05 EDT 
Checked sources of several pages manually. There are no custom exo:* attributes. W3c validation script passed. Tested with 6.2.0.ER2.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.