This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28497 - In 15.1, one of the obsolete features is:
Summary: In 15.1, one of the obsolete features is:
Status: RESOLVED WORKSFORME
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: https://html.spec.whatwg.org/#obsolete
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-16 05:52 UTC by contributor
Modified: 2015-08-28 15:52 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2015-04-16 05:52:57 UTC 
Specification: https://html.spec.whatwg.org/multipage/obsolete.html
Multipage: https://html.spec.whatwg.org/multipage/#obsolete
Complete: https://html.spec.whatwg.org/#obsolete
Referrer: https://html.spec.whatwg.org/multipage/index.html

Comment:
In 15.1, one of the obsolete features is:
Authors should not specify a border attribute on an img element. If the
attribute is present, its value *must* be the string "0".

... but in 15.1.1 the trigger for a warning is:
The presence of a border attribute on an img element if its value is the
string "0".

... so, which is acceptable?  ="0" or not="0" ?

Posted from: 66.191.156.48
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0
Comment 1 Simon Pieters 2015-04-16 07:59:36 UTC 
Warning: border=0
Error: border=1
Comment 2 Ian 'Hixie' Hickson 2015-04-16 22:15:51 UTC 
Yeah, what Simon said. Neither is "acceptable".