title-trigger - Revision history

AndyMabbett: /* Semantics */ refute last

2007-08-17T19:28:31Z

Semantics: refute last

← Older revision		Revision as of 19:28, 17 August 2007
Line 47:		Line 47:
	===Semantics===		===Semantics===

	HTML is a markup language: its elements and attributes are intended to be descriptive. They are descriptors rather than commands. The proposed usage of the <code>class</code> attribute would be an instruction rather than a description (somewhat like the <code>target</code> attribute, now deprecated). This would be an abuse of the semantics of the <code>class</code> attribute.		HTML is a markup language: its elements and attributes are intended to be descriptive. They are descriptors rather than commands. The proposed usage of the <code>class</code> attribute would be an instruction rather than a description (somewhat like the <code>target</code> attribute, now deprecated). This would be an abuse of the semantics of the <code>class</code> attribute. (Comment by [[User:Adactio]])
			*Not if the class name is read as "microformat usable title" [[User:AndyMabbett\|Andy Mabbett]]

	===Parsers===		===Parsers===

2007-08-17T12:01:28Z

Semantics

← Older revision		Revision as of 12:01, 17 August 2007
Line 47:		Line 47:
	===Semantics===		===Semantics===

	~~No known or perceived issues~~.		HTML is a markup language: its elements and attributes are intended to be descriptive. They are descriptors rather than commands. The proposed usage of the <code>class</code> attribute would be an instruction rather than a description (somewhat like the <code>target</code> attribute, now deprecated). This would be an abuse of the semantics of the <code>class</code> attribute.

	===Parsers===		===Parsers===

2007-08-16T23:53:57Z

Assistive technology

← Older revision		Revision as of 23:53, 16 August 2007
Line 59:		Line 59:
	===Assistive technology===		===Assistive technology===

	The proposed solution assumes that screen readers don't treat <code>title</code> as a special case on elements other than <code>abbr</code> or <code>acronym</code> (or perhaps <code>a</code> and <code>img</code>, which may need to be excluded from the solution) even so, the use of the special class name would be optional in such cases.		The proposed solution assumes that screen readers don't treat <code>title</code> as a special case on elements other than <code>abbr</code> or <code>acronym</code> (or perhaps <code>a</code> and <code>img</code>, which may need to be excluded from the solution) even so, the use of the special class name would be optional in such cases; and suitable guidance should be given to editors.

	Is this actually the case? Please create a page for [[assistive-technology-title-trigger-results\|assistive technology title trigger results]] and add the results of testing there.		Is this actually the case? Please create a page for [[assistive-technology-title-trigger-results\|assistive technology title trigger results]] and add the results of testing there.

2007-08-16T23:52:59Z

← Older revision		Revision as of 23:52, 16 August 2007
Line 57:		Line 57:
	No known or perceived issues.		No known or perceived issues.

	===Assistive ~~Technology~~===		===Assistive technology===

	The proposed ~~solutioneen~~ readers don't treat <code>title</code> as a special case on elements other than <code>abbr</code> or <code>acronym</code> (or perhaps <code>a</code> and <code>img</code>, which may need to be excluded from the solution). Is this actually the case? Please create a page for [[assistive-technology-title-trigger-results\|assistive technology title trigger results]] and add the results of testing there.		The proposed solution assumes that screen readers don't treat <code>title</code> as a special case on elements other than <code>abbr</code> or <code>acronym</code> (or perhaps <code>a</code> and <code>img</code>, which may need to be excluded from the solution) even so, the use of the special class name would be optional in such cases.

			Is this actually the case? Please create a page for [[assistive-technology-title-trigger-results\|assistive technology title trigger results]] and add the results of testing there.

	===Usage in the wild===		===Usage in the wild===

2007-08-16T23:50:58Z

Issues

@@ Line 43: / Line 43: @@
 *Easy for parsers to adapt
-==Disadvantages==
+==Issues==
-* ???
 ==Alternatives==

2007-08-16T23:45:57Z

fmt

← Older revision		Revision as of 23:45, 16 August 2007
Line 9:		Line 9:
	==Proposal==		==Proposal==

	Use a class name; say "ufusetitle" (for "microformat, use title") or something equally unlikely to otherwise occur in the wild, on any element, to trigger the use of that element's <code>title</code> attribute.		Use a class name; say "ufusetitle" (for "microformat, use title") or something equally unlikely to otherwise occur in the wild, on any element, to trigger the use of that element's <code>title</code> attribute. e.g.

	~~e.g.~~ <nowiki><span class="dtstart ufusetitle" title="2007-08-16">16th August this year</span></nowiki>		<pre>
			<nowiki>
			<span
			class="dtstart ufusetitle"
			title="2007-08-16"
			>

			16th August this year

			</span>
			</nowiki>
			</pre>

	===Conversion===		===Conversion===

2007-08-16T23:45:09Z

← Older revision		Revision as of 23:45, 16 August 2007
Line 9:		Line 9:
	==Proposal==		==Proposal==

	Use a class name; say "ufusetitle" (for "microformat, use title") or something equally unlikely to otherwise occur in the wild, on any element, to trigger the use of ~~the~~ <code>title</code> attribute.		Use a class name; say "ufusetitle" (for "microformat, use title") or something equally unlikely to otherwise occur in the wild, on any element, to trigger the use of that element's <code>title</code> attribute.

	e.g. <nowiki><span class="dtstart ufusetitle" title="2007-08-16">16th August this year</span></nowiki>		e.g. <nowiki><span class="dtstart ufusetitle" title="2007-08-16">16th August this year</span></nowiki>
Line 15:		Line 15:
	===Conversion===		===Conversion===
	All existing and new microformats should use this pattern; abbr-design-pattern should be deprecated, but parsers should still be required to recognise it on legacy pages (perhaps for a period of, say, three years)		All existing and new microformats should use this pattern; abbr-design-pattern should be deprecated, but parsers should still be required to recognise it on legacy pages (perhaps for a period of, say, three years)


	==Class names==		==Class names==

2007-08-16T23:37:07Z

Advantages: simple!

← Older revision		Revision as of 23:37, 16 August 2007
Line 26:		Line 26:

	==Advantages==		==Advantages==
			*Simple
	*Works on any element		*Works on any element
	*Usable on CMSs (e.g. MediaWiki) which do not allow use of <code>abbr</code>		*Usable on CMSs (e.g. MediaWiki) which do not allow use of <code>abbr</code>
			*Easy to learn
	*Ease of authoring		*Ease of authoring
	*Easy to learn
	*Easy for parsers to adapt		*Easy for parsers to adapt

2007-08-16T23:33:53Z

Advantages: +2

← Older revision		Revision as of 23:33, 16 August 2007
Line 28:		Line 28:
	*Works on any element		*Works on any element
	*Usable on CMSs (e.g. MediaWiki) which do not allow use of <code>abbr</code>		*Usable on CMSs (e.g. MediaWiki) which do not allow use of <code>abbr</code>
			*Ease of authoring
			*Easy to learn
	*Easy for parsers to adapt		*Easy for parsers to adapt

2007-08-16T23:33:16Z

Class names: uftitletrigger