Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 365800 - [content model] Wrong obsolete warning on table border attribute in HTML 5
Summary: [content model] Wrong obsolete warning on table border attribute in HTML 5
Status: RESOLVED FIXED
Alias: None
Product: WTP Source Editing
Classification: WebTools
Component: wst.html (show other bugs)
Version: 3.3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.3.2   Edit
Assignee: Nick Sandonato CLA
QA Contact: Nick Sandonato CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-06 14:55 EST by Menachem Salomon CLA
Modified: 2011-12-06 15:25 EST (History)
1 user (show)

See Also:

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

Note You need to log in before you can comment on or make changes to this bug.
Description Menachem Salomon CLA 2011-12-06 14:55:10 EST 
Build Identifier: Version: 3.6.2 Build id: M20110210-1200

The border attribute of the table tag is incorrectly labeled as "obsolete", even when the value is set to "1".  Although the border attribute with other values is indeed obsolete, values "" and "1" are still permitted.  The warning is overly strict.

Reproducible: Always

Steps to Reproduce:
<!DOCTYPE html>        <!-- to announce intention to use HTML 5 -->
<html><head></head>
<body>
    <table border="1"><tr><td>Blah</td></tr></table>
</body> </html>
Comment 1 Nick Sandonato CLA 2011-12-06 15:19:47 EST 
Content model changes delivered. Thanks, Menachem.
Comment 2 Menachem Salomon CLA 2011-12-06 15:22:06 EST 
(In reply to comment #1)
> Content model changes delivered. Thanks, Menachem.

Will the change apply to JSP as well? As it happens, that's where I initially noticed the issue.
Comment 3 Nick Sandonato CLA 2011-12-06 15:25:50 EST 
(In reply to comment #2)
> (In reply to comment #1)
> > Content model changes delivered. Thanks, Menachem.
> 
> Will the change apply to JSP as well? As it happens, that's where I initially
> noticed the issue.

Yup, it'll work for JSPs as well.