Talk:Reviewing - Revision history

Annevk: moved Talk:Reviewing HTML5 to Talk:Reviewing: these reviewing tips apply to all specs

2011-01-26T08:08:51Z

moved Talk:Reviewing HTML5 to Talk:Reviewing: these reviewing tips apply to all specs

← Older revision	Revision as of 08:08, 26 January 2011
(No difference)

TheresaOConnor: Reverted edits by Shaeha (talk) to last revision by EdwardOConnor

2010-09-15T15:46:20Z

Reverted edits by Shaeha (talk) to last revision by EdwardOConnor

← Older revision		Revision as of 15:46, 15 September 2010
Line 451:		Line 451:
	the text of the numbers for autogenerated content. <textareas> could also have numbering; this is very useful for matching up error messages with lines of markedup text when a wysiwyg editor is not used (for example, in a wiki); also, this is compatible with javascript wysiwig editors that take over a text area. Low priority, but worth mentioning.		the text of the numbers for autogenerated content. <textareas> could also have numbering; this is very useful for matching up error messages with lines of markedup text when a wysiwyg editor is not used (for example, in a wiki); also, this is compatible with javascript wysiwig editors that take over a text area. Low priority, but worth mentioning.
	~~~~		~~~~

	~~==Related Links==~~

	~~[http://cargames.com.au/ '''car games''']~~

	~~[http://www.unbeatable.co.uk/pages/Electronics/TV-and-Video/Flat-Panel-Televisions/ '''lcd tv''']~~

Shaeha at 06:18, 15 September 2010

2010-09-15T06:18:49Z

← Older revision		Revision as of 06:18, 15 September 2010
Line 451:		Line 451:
	the text of the numbers for autogenerated content. <textareas> could also have numbering; this is very useful for matching up error messages with lines of markedup text when a wysiwyg editor is not used (for example, in a wiki); also, this is compatible with javascript wysiwig editors that take over a text area. Low priority, but worth mentioning.		the text of the numbers for autogenerated content. <textareas> could also have numbering; this is very useful for matching up error messages with lines of markedup text when a wysiwyg editor is not used (for example, in a wiki); also, this is compatible with javascript wysiwig editors that take over a text area. Low priority, but worth mentioning.
	~~~~		~~~~

			==Related Links==

			[http://cargames.com.au/ '''car games''']

			[http://www.unbeatable.co.uk/pages/Electronics/TV-and-Video/Flat-Panel-Televisions/ '''lcd tv''']

TheresaOConnor: reverting spam

2010-07-26T15:21:01Z

reverting spam

← Older revision		Revision as of 15:21, 26 July 2010
Line 451:		Line 451:
	the text of the numbers for autogenerated content. <textareas> could also have numbering; this is very useful for matching up error messages with lines of markedup text when a wysiwyg editor is not used (for example, in a wiki); also, this is compatible with javascript wysiwig editors that take over a text area. Low priority, but worth mentioning.		the text of the numbers for autogenerated content. <textareas> could also have numbering; this is very useful for matching up error messages with lines of markedup text when a wysiwyg editor is not used (for example, in a wiki); also, this is compatible with javascript wysiwig editors that take over a text area. Low priority, but worth mentioning.
	~~~~		~~~~
	~~<br>~~
	~~==Related Links==~~

	~~[http://www.cellulite.co.uk/ '''cellulite''']~~

Jheena789 at 11:06, 26 July 2010

2010-07-26T11:06:44Z

← Older revision		Revision as of 11:06, 26 July 2010
Line 451:		Line 451:
	the text of the numbers for autogenerated content. <textareas> could also have numbering; this is very useful for matching up error messages with lines of markedup text when a wysiwyg editor is not used (for example, in a wiki); also, this is compatible with javascript wysiwig editors that take over a text area. Low priority, but worth mentioning.		the text of the numbers for autogenerated content. <textareas> could also have numbering; this is very useful for matching up error messages with lines of markedup text when a wysiwyg editor is not used (for example, in a wiki); also, this is compatible with javascript wysiwig editors that take over a text area. Low priority, but worth mentioning.
	~~~~		~~~~
			<br>
	==Related Links==		==Related Links==

	[http://www.cellulite.co.uk/ '''cellulite''']		[http://www.cellulite.co.uk/ '''cellulite''']

Jheena789 at 11:06, 26 July 2010

2010-07-26T11:06:12Z

← Older revision		Revision as of 11:06, 26 July 2010
Line 451:		Line 451:
	the text of the numbers for autogenerated content. <textareas> could also have numbering; this is very useful for matching up error messages with lines of markedup text when a wysiwyg editor is not used (for example, in a wiki); also, this is compatible with javascript wysiwig editors that take over a text area. Low priority, but worth mentioning.		the text of the numbers for autogenerated content. <textareas> could also have numbering; this is very useful for matching up error messages with lines of markedup text when a wysiwyg editor is not used (for example, in a wiki); also, this is compatible with javascript wysiwig editors that take over a text area. Low priority, but worth mentioning.
	~~~~		~~~~

			==Related Links==

			[http://www.cellulite.co.uk/ '''cellulite''']

Whitis: multiple comments: datagrid/fold/tabs, video, canvas, compass, 9-slice, pre/textarea line numbers

2009-05-07T09:43:13Z

multiple comments: datagrid/fold/tabs, video, canvas, compass, 9-slice, pre/textarea line numbers

Show changes

Whitis: reply re do_not_format_source

2009-05-07T07:25:34Z

reply re do_not_format_source

← Older revision		Revision as of 07:25, 7 May 2009
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)

Hixie at 21:55, 6 May 2009

2009-05-06T21:55:14Z

← Older revision		Revision as of 21:55, 6 May 2009
Line 5:		Line 5:

	[[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)

Whitis: do_not_reformat_source tag

2009-05-06T21:51:00Z

do_not_reformat_source tag

New page

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.

[[User:Whitis|Whitis]] 21:51, 6 May 2009 (UTC)