A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).

Talk:Reviewing: Difference between revisions

From WHATWG Wiki
Jump to navigation Jump to search
No edit summary
(reply re do_not_format_source)
Line 6: Line 6:
[[User:Whitis|Whitis]] 21:51, 6 May 2009 (UTC)
[[User:Whitis|Whitis]] 21:51, 6 May 2009 (UTC)


I would recommend asking the developers of the tools you use (e.g. tidy) to support a "class" value that would do this, that way it can work even with HTML4 documents, no need to add an element or anything. [[User:Hixie|Hixie]] 21:55, 6 May 2009 (UTC)
I would recommend asking the developers of the tools you use (e.g. tidy) to support a "class" value that would do this, that way it can work even with HTML4 documents, no need to add an element or anything. [[User:Hixie|Hixie]] 21:55, 6 May 2009 (UTC) 
 
  No good. That would be specific to individual tools.    There needs to be a standard used by all tools.  If you want to
  include a standard class instead of a tag, that is fine.  But it should be mentioned in the markup spec as that is one
  document that all the the tool developers will read. 
    <div class="do_not_reformat_source">...</div>
  Consider this a source code accessibility issue.
  [[User:Whitis|Whitis]] 07:25, 7 May 2009 (UTC)

Revision as of 07:25, 7 May 2009

Suggest a new tag:

 <do_not_reformat_source>
 </do_not_reformat_source>

To provide a standardize way to tell tools like html tidy that the code in that section should not be reformatted without an explicit override. It would do nothing in the browser. Some markup is best left as is. For example, tables, embedded structured data, etc.

Whitis 21:51, 6 May 2009 (UTC)

I would recommend asking the developers of the tools you use (e.g. tidy) to support a "class" value that would do this, that way it can work even with HTML4 documents, no need to add an element or anything. Hixie 21:55, 6 May 2009 (UTC)

  No good. That would be specific to individual tools.    There needs to be a standard used by all tools.   If you want to
  include a standard class instead of a tag, that is fine.   But it should be mentioned in the markup spec as that is one 
  document that all the the tool developers will read.  
...
  Consider this a source code accessibility issue.
  Whitis 07:25, 7 May 2009 (UTC)