W3C home > Mailing lists > Public > www-validator-cvs@w3.org > February 2014

[Bug 24559] Nu Markup Checker emits "Use CSS instead" help message for table@border=1

From: <bugzilla@jessica.w3.org>
Date: Thu, 06 Feb 2014 10:52:30 +0000
To: www-validator-cvs@w3.org
Message-ID: <bug-24559-169-aY0jwVQ6m9@http.www.w3.org/Bugs/Public/>

Michael[tm] Smith <mike@w3.org> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
                 CC|                            |mike@w3.org
         Resolution|---                         |NEEDSINFO
            Summary|table="border" is           |Nu Markup Checker emits
                   |conforming because a change |"Use CSS instead" help
                   |proposal placed it back     |message for table@border=1
                   |into the spec (long ago)    |

--- Comment #1 from Michael[tm] Smith <mike@w3.org> ---
I'm pasting below are my comments so far from the related www-validator thread,
and moving the bug to resolved=needsinfo awaiting the response. Note that the
document under discussion (the document the OP cited in the www-validator
thread) is at http://www.w3.org/TR/2014/PR-rdf11-mt-20140109/

As I understand it, you're probably suggesting I should try to answer the
question of why, in the particular document that the OP cited, using legacy
table@border=1 markup for presentational purposes is a better choice than
following the normal longstanding recommended best practice of just using a
couple lines of CSS to achieve the same presentational effect -

  table { border-style: outset; border-width: 1px; border-spacing: 2px; }
  table td { border-style: inset; border-width: 1px; }

Problem is, in looking at the particular document the OP cited, I don't see
any reason why he couldn't or shouldn't be using CSS instead. Can you?

I admit I may be missing something. So can you elaborate on why, for the
particular document the OP cited -- in which to me at least it seems the OP
clearly has no special restrictions preventing him from using CSS instead
of table@border=1 -- he shouldn't choose to add a couple lines of CSS?

The reason the Nu Markup Checker emits a message for table@border=1 is to
make authors aware that their markup may run counter to best practice, and
so help authors make an informed choice for what to do about it. If we don't
emit any message, then we're not making the author aware of the potential
problem in the doc, and not helping them to make an informed choice.

Or do you disagree? Should we not be trying to help the author make an
informed choice here? Are you saying that for authors who want table
borders and can easily add them using CSS (to go along with the normal
best-practice guidelines that all the experts have recommended for many
years now), they should always just be using table@border=1 instead?

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 6 February 2014 10:52:31 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:17:56 UTC