abbr-design-pattern-issues - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:20:43Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:20, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~abbr design pattern issues~~</entry-title>~~		{{DISPLAYTITLE:abbr design pattern issues}}

	These are externally raised issues about [[abbr-design-pattern]] with broadly varying degrees of merit. Thus some issues may be REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec.		These are externally raised issues about [[abbr-design-pattern]] with broadly varying degrees of merit. Thus some issues may be REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec.

Tantek: entry-title, auto-toc, resolved and close few outstanding issues that were long ago resolved (or made irrelevant), and move resolved and closed issues to separate pages

2011-10-27T00:15:25Z

entry-title, auto-toc, resolved and close few outstanding issues that were long ago resolved (or made irrelevant), and move resolved and closed issues to separate pages

@@ Line 1: / Line 1: @@
-<h1>abbr design pattern issues</h1>
+<entry-title>abbr design pattern issues</entry-title>
 These are externally raised issues about [[abbr-design-pattern]] with broadly varying degrees of merit. Thus some issues may be REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec.
@@ Line 9: / Line 9: @@
 Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.
-__TOC__
+== Closed Issues ==
 == Issues ==
+No open issues currently.
 == Template ==
-Please use this format (copy and paste this to the end of the list to add your issues):
+{{issues-format}}
 == See Also ==
 * [[abbr-design-pattern]]
 * [[accessibility-issues]]
 * [[dfn-design-pattern]] (proposal)

Brian: Reverted edits by RelelTbocd (Talk) to last version by AmeerDawood

2008-12-20T20:50:42Z

Reverted edits by RelelTbocd (Talk) to last version by AmeerDawood

← Older revision		Revision as of 20:50, 20 December 2008
Line 1:		Line 1:
	~~cgetoloc~~
	<h1>abbr design pattern issues</h1>		<h1>abbr design pattern issues</h1>

Line 6:		Line 5:
	<!-- '''IMPORTANT''': Please read the [[abbr-design-pattern-faq\|abbr-design-pattern FAQ]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered. -->		<!-- '''IMPORTANT''': Please read the [[abbr-design-pattern-faq\|abbr-design-pattern FAQ]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered. -->

	Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. ~~â~~ [http://tantek.com/ Tantek]		Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]

	Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.		Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

RelelTbocd: cotroc

2008-12-19T03:37:43Z

cotroc

← Older revision		Revision as of 03:37, 19 December 2008
Line 1:		Line 1:
			cgetoloc
	<h1>abbr design pattern issues</h1>		<h1>abbr design pattern issues</h1>

Line 5:		Line 6:
	<!-- '''IMPORTANT''': Please read the [[abbr-design-pattern-faq\|abbr-design-pattern FAQ]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered. -->		<!-- '''IMPORTANT''': Please read the [[abbr-design-pattern-faq\|abbr-design-pattern FAQ]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered. -->

	Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]		Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. â [http://tantek.com/ Tantek]

	Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.		Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

AmeerDawood: /* Issues */

2008-11-17T23:50:16Z

Issues

← Older revision		Revision as of 23:50, 17 November 2008
Line 21:		Line 21:

	* {{OpenIssue}} 2008-01-01 raised by [[User:AndyMabbett\|Andy Mabbett]].		* {{OpenIssue}} 2008-01-01 raised by [[User:AndyMabbett\|Andy Mabbett]].
	*# How are empty (<code>title=""</code>) title attributes to be parsed? At the time of writing, X2V returns a null value; Operator uses the content of the abbr element. Such mark-up is valid, but semantically illogical. The former parser ~~behaviour~~ seems the most logical, but results in an invalid vCard. See [http://www.westmidlandbirdclub.com/test example].		*# How are empty (<code>title=""</code>) title attributes to be parsed? At the time of writing, X2V returns a null value; Operator uses the content of the abbr element. Such mark-up is valid, but semantically illogical. The former parser behavior seems the most logical, but results in an invalid vCard. See [http://www.westmidlandbirdclub.com/test example].

	* {{OpenIssue}} 2008-01-01 raised by [[User:AndyMabbett\|Andy Mabbett]].		* {{OpenIssue}} 2008-01-01 raised by [[User:AndyMabbett\|Andy Mabbett]].

Brian: /* Issues */

2008-05-15T10:16:43Z

Issues

← Older revision		Revision as of 10:16, 15 May 2008
Line 28:		Line 28:
	* {{OpenIssue}} 2008-05-14 raised by [[User:LeeJordan\|Lee Jordan]].		* {{OpenIssue}} 2008-05-14 raised by [[User:LeeJordan\|Lee Jordan]].
	*# Search Engines indexing pages using abbr-design-design pattern may expand the title attribute in the text indexed for the description part of the search result. An example from a recent page created which was indexed by Google and included a hCalendar event marked up with the class dtstart: 2008-04-2121st April 2008. Notice the lack of white space between the dates? Perhaps search engines work in a similar way as assistive technology like screen readers in expanding abbreviations but but fail to add brackets around the abbreviation text or fail to suppress one or the other.		*# Search Engines indexing pages using abbr-design-design pattern may expand the title attribute in the text indexed for the description part of the search result. An example from a recent page created which was indexed by Google and included a hCalendar event marked up with the class dtstart: 2008-04-2121st April 2008. Notice the lack of white space between the dates? Perhaps search engines work in a similar way as assistive technology like screen readers in expanding abbreviations but but fail to add brackets around the abbreviation text or fail to suppress one or the other.
			** Please supply an example in the wild to further determine/confirm this is an issue with the mark-up/spider/search engine

	* See also [[accessibility-issues#abbr-design-pattern]].		* See also [[accessibility-issues#abbr-design-pattern]].

Lee Jordan: /* Issues */

2008-05-14T10:40:50Z

Issues

← Older revision		Revision as of 10:40, 14 May 2008
Line 25:		Line 25:
	* {{OpenIssue}} 2008-01-01 raised by [[User:AndyMabbett\|Andy Mabbett]].		* {{OpenIssue}} 2008-01-01 raised by [[User:AndyMabbett\|Andy Mabbett]].
	*# How are missing title attributes to be parsed? This is both valid and semantically-meaningful mark-up (the content is an abbreviation, but we know not of what) At the time of writing, X2V and Operator both use the content of the abbr element; this seems sensible, and should, perhaps, be ratified in the spec. See [http://www.westmidlandbirdclub.com/test example].		*# How are missing title attributes to be parsed? This is both valid and semantically-meaningful mark-up (the content is an abbreviation, but we know not of what) At the time of writing, X2V and Operator both use the content of the abbr element; this seems sensible, and should, perhaps, be ratified in the spec. See [http://www.westmidlandbirdclub.com/test example].

			* {{OpenIssue}} 2008-05-14 raised by [[User:LeeJordan\|Lee Jordan]].
			*# Search Engines indexing pages using abbr-design-design pattern may expand the title attribute in the text indexed for the description part of the search result. An example from a recent page created which was indexed by Google and included a hCalendar event marked up with the class dtstart: 2008-04-2121st April 2008. Notice the lack of white space between the dates? Perhaps search engines work in a similar way as assistive technology like screen readers in expanding abbreviations but but fail to add brackets around the abbreviation text or fail to suppress one or the other.

	* See also [[accessibility-issues#abbr-design-pattern]].		* See also [[accessibility-issues#abbr-design-pattern]].

PaTrick: /* Issues */

2008-02-04T12:44:08Z

Issues

← Older revision		Revision as of 12:44, 4 February 2008
Line 15:		Line 15:

	* {{OpenIssue}} 2008-02-04 raised by [[User:PaTrick\|Patrick van Aalst]].		* {{OpenIssue}} 2008-02-04 raised by [[User:PaTrick\|Patrick van Aalst]].
	*# The <nowiki><ABBR></nowiki> tag is not supported by IE6; to style it, you'll need to include extra html, for example: <abbr title="2008-01-16T15:00:00-01:00"><span class="dtstart">16 januari 2008</span></abbr>.		*# The <nowiki><ABBR></nowiki> tag is not supported by IE6; to style it, you'll need to include extra html, for example: <nowiki><abbr title="2008-01-16T15:00:00-01:00"><span class="dtstart">16 januari 2008</span></abbr></nowiki>.

	* {{OpenIssue}} 2008-01-01 raised by [[User:AndyMabbett\|Andy Mabbett]].		* {{OpenIssue}} 2008-01-01 raised by [[User:AndyMabbett\|Andy Mabbett]].

PaTrick: /* Issues */

2008-02-04T12:43:48Z

Issues

← Older revision		Revision as of 12:43, 4 February 2008
Line 12:		Line 12:

	== Issues ==		== Issues ==


			* {{OpenIssue}} 2008-02-04 raised by [[User:PaTrick\|Patrick van Aalst]].
			*# The <nowiki><ABBR></nowiki> tag is not supported by IE6; to style it, you'll need to include extra html, for example: <abbr title="2008-01-16T15:00:00-01:00"><span class="dtstart">16 januari 2008</span></abbr>.

	* {{OpenIssue}} 2008-01-01 raised by [[User:AndyMabbett\|Andy Mabbett]].		* {{OpenIssue}} 2008-01-01 raised by [[User:AndyMabbett\|Andy Mabbett]].

AndyMabbett: /* Issues */ .

2008-01-01T17:13:10Z

Issues: .

← Older revision		Revision as of 17:13, 1 January 2008
Line 14:		Line 14:

	* {{OpenIssue}} 2008-01-01 raised by [[User:AndyMabbett\|Andy Mabbett]].		* {{OpenIssue}} 2008-01-01 raised by [[User:AndyMabbett\|Andy Mabbett]].
	*# Abbreviations in the middle of microformat element values should be parsed? e.g for <code><nowiki><span class="street-address">New John <abbr title="Street">St.</abbr> West</span></nowiki></code>, both Operator and X2V return, at the time of writing, vCards containing "New John St. West", not the expected "New John Street West". Data is thus being lost. See [http://www.westmidlandbirdclub.com/test example].		*# Abbreviations in the middle of microformat element values should be parsed. e.g for <code><nowiki><span class="street-address">New John <abbr title="Street">St.</abbr> West</span></nowiki></code>, both Operator and X2V return, at the time of writing, vCards containing "New John St. West", not the expected "New John Street West". Data is thus being lost. See [http://www.westmidlandbirdclub.com/test example].

	* {{OpenIssue}} 2008-01-01 raised by [[User:AndyMabbett\|Andy Mabbett]].		* {{OpenIssue}} 2008-01-01 raised by [[User:AndyMabbett\|Andy Mabbett]].