Extensions - Revision history

GPHemsley: added Category:Proposals using HotCat

2013-07-09T14:06:49Z

← Older revision		Revision as of 14:06, 9 July 2013
Line 280:		Line 280:
	* Is it OK to switch parsing mode mid-document like this (and to effectively require an XML parser in every UA)?		* Is it OK to switch parsing mode mid-document like this (and to effectively require an XML parser in every UA)?
	** Why not? If a UA implements this new syntax, and claims to support for example MathML or SVG, then of course it needs to be able to parse XML.		** Why not? If a UA implements this new syntax, and claims to support for example MathML or SVG, then of course it needs to be able to parse XML.

			[[Category:Proposals]]

Etan Wexler: Caveat lector about Microsoft’s whitepaper

2009-03-16T04:46:58Z

Caveat lector about Microsoft’s whitepaper

← Older revision		Revision as of 04:46, 16 March 2009
Line 178:		Line 178:
	== Proposal 3: XML5 ==		== Proposal 3: XML5 ==

	Microsoft has published a whitepaper, [http://code.msdn.microsoft.com/Project/Download/FileDownload.aspx?ProjectName=ie8whitepapers&DownloadId=1042 “Improved Namespace Support”]. Salient features:		Microsoft has published a whitepaper, [http://code.msdn.microsoft.com/Project/Download/FileDownload.aspx?ProjectName=ie8whitepapers&DownloadId=1042 “Improved Namespace Support”], purporting to describe features of Windows Internet Explorer 8 beta 1. Caveat lector: the whitepaper reflects views that held sway within Microsoft Corporation at the time of publication (2008-03). The whitepaper disclaims both the accuracy of the whitepaper after its publication and organizational commitment to the features therein described.

			Salient features:

	* Windows Internet Explorer 8 Beta 1 for Developers offers Web developers the opportunity to write standards-compliant HTML-based Web pages that support features (such as SVG, XUL, and MathML) in namespaces, ''provided that the client has installed appropriate handlers for those namespaces via binary behaviors''. (A binary behavior is a type of ActiveX control.) ''<ins>[[User:Tbroyer\|Tbroyer]]: note that those ''behaviors'' don't change the way the markup is parsed into a DOM; at least for elements whose name contains a colon (haven't tested this in IE8, but this is the way it is since IE5.5)</ins>''		* Windows Internet Explorer 8 Beta 1 for Developers offers Web developers the opportunity to write standards-compliant HTML-based Web pages that support features (such as SVG, XUL, and MathML) in namespaces, ''provided that the client has installed appropriate handlers for those namespaces via binary behaviors''. (A binary behavior is a type of ActiveX control.) ''<ins>[[User:Tbroyer\|Tbroyer]]: note that those ''behaviors'' don't change the way the markup is parsed into a DOM; at least for elements whose name contains a colon (haven't tested this in IE8, but this is the way it is since IE5.5)</ins>''

Etan Wexler: Improvements to anchor text about Microsoft’s whitepaper

2009-03-16T04:27:22Z

Improvements to anchor text about Microsoft’s whitepaper

← Older revision		Revision as of 04:27, 16 March 2009
Line 178:		Line 178:
	== Proposal 3: XML5 ==		== Proposal 3: XML5 ==

	Microsoft has published a [http://code.msdn.microsoft.com/Project/Download/FileDownload.aspx?ProjectName=ie8whitepapers&DownloadId=1042 ~~whitepaper~~] ~~on the subject of ''Improved Namespace Support''~~. Salient features:		Microsoft has published a whitepaper, [http://code.msdn.microsoft.com/Project/Download/FileDownload.aspx?ProjectName=ie8whitepapers&DownloadId=1042 “Improved Namespace Support”]. Salient features:

	* Windows Internet Explorer 8 Beta 1 for Developers offers Web developers the opportunity to write standards-compliant HTML-based Web pages that support features (such as SVG, XUL, and MathML) in namespaces, ''provided that the client has installed appropriate handlers for those namespaces via binary behaviors''. (A binary behavior is a type of ActiveX control.) ''<ins>[[User:Tbroyer\|Tbroyer]]: note that those ''behaviors'' don't change the way the markup is parsed into a DOM; at least for elements whose name contains a colon (haven't tested this in IE8, but this is the way it is since IE5.5)</ins>''		* Windows Internet Explorer 8 Beta 1 for Developers offers Web developers the opportunity to write standards-compliant HTML-based Web pages that support features (such as SVG, XUL, and MathML) in namespaces, ''provided that the client has installed appropriate handlers for those namespaces via binary behaviors''. (A binary behavior is a type of ActiveX control.) ''<ins>[[User:Tbroyer\|Tbroyer]]: note that those ''behaviors'' don't change the way the markup is parsed into a DOM; at least for elements whose name contains a colon (haven't tested this in IE8, but this is the way it is since IE5.5)</ins>''

Etan Wexler: Correction to the address of Microsoft’s whitepaper

2009-03-16T04:20:11Z

Correction to the address of Microsoft’s whitepaper

← Older revision		Revision as of 04:20, 16 March 2009
Line 178:		Line 178:
	== Proposal 3: XML5 ==		== Proposal 3: XML5 ==

	Microsoft has published a [http://code.msdn.microsoft.com/~~Release~~/~~ProjectReleases~~.aspx?ProjectName=ie8whitepapers&~~ReleaseId~~=~~573~~ whitepaper] on the subject of ''Improved Namespace Support''. Salient features:		Microsoft has published a [http://code.msdn.microsoft.com/Project/Download/FileDownload.aspx?ProjectName=ie8whitepapers&DownloadId=1042 whitepaper] on the subject of ''Improved Namespace Support''. Salient features:

	* Windows Internet Explorer 8 Beta 1 for Developers offers Web developers the opportunity to write standards-compliant HTML-based Web pages that support features (such as SVG, XUL, and MathML) in namespaces, ''provided that the client has installed appropriate handlers for those namespaces via binary behaviors''. (A binary behavior is a type of ActiveX control.) ''<ins>[[User:Tbroyer\|Tbroyer]]: note that those ''behaviors'' don't change the way the markup is parsed into a DOM; at least for elements whose name contains a colon (haven't tested this in IE8, but this is the way it is since IE5.5)</ins>''		* Windows Internet Explorer 8 Beta 1 for Developers offers Web developers the opportunity to write standards-compliant HTML-based Web pages that support features (such as SVG, XUL, and MathML) in namespaces, ''provided that the client has installed appropriate handlers for those namespaces via binary behaviors''. (A binary behavior is a type of ActiveX control.) ''<ins>[[User:Tbroyer\|Tbroyer]]: note that those ''behaviors'' don't change the way the markup is parsed into a DOM; at least for elements whose name contains a colon (haven't tested this in IE8, but this is the way it is since IE5.5)</ins>''
Line 195:		Line 195:

	I've no idea what IE8 beta 1 is supposed to do. The whitepaper doesn't describe the processing model, the error handling, or how to handle legacy content, and IE8 Beta 1 doesn't seem to implement the whitepaper's syntax at all.		I've no idea what IE8 beta 1 is supposed to do. The whitepaper doesn't describe the processing model, the error handling, or how to handle legacy content, and IE8 Beta 1 doesn't seem to implement the whitepaper's syntax at all.


	== Proposal 4: XML inside comments ==		== Proposal 4: XML inside comments ==

Shepazu: added "type" to element

2008-05-28T13:44:46Z

added "type" to <ext> element

← Older revision		Revision as of 13:44, 28 May 2008
Line 42:		Line 42:
	<pre>		<pre>
	<p>Hello world.		<p>Hello world.
	<ext>		<ext type="image/svg+xml">
	<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 10 10">		<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 10 10">
	<circle x="5" y="5 r="5" stroke="green"/>		<circle x="5" y="5 r="5" stroke="green"/>
Line 131:		Line 131:
	<h1 id="test_of_extensibility">Test of Extensibility</h1>		<h1 id="test_of_extensibility">Test of Extensibility</h1>
	<p>This is a test of an extensibility point in text/html, with a fallback mechanism.</p>		<p>This is a test of an extensibility point in text/html, with a fallback mechanism.</p>
	<ext>		<ext type="image/svg+xml">
	<fallback>		<fallback>
	<img src="anIsland.png" alt="..."/>		<img src="anIsland.png" alt="..."/>

Eirik: /* Proposal 4: XML inside comments */

2008-04-04T20:07:11Z

Proposal 4: XML inside comments

← Older revision		Revision as of 20:07, 4 April 2008
Line 254:		Line 254:
	Example 3. (No fallback)		Example 3. (No fallback)
	<pre>		<pre>
	<!--[if accepts ~~text~~/~~mathml~~]>		<!--[if accepts image/svg+xml]>
	<~~math~~ xmlns="http://www.w3.org/~~1998~~/~~Math/MathML~~">		<svg xmlns="http://www.w3.org/2000/svg" version="1.1">
	~~<mn>2</mn>~~		<circle r="100" fill="red" stroke="blue" />
	~~<mi>x~~</mi>		</svg>
	</~~math~~>
	<![endif]-->		<![endif]-->
	</pre>		</pre>

Eirik: /* Proposal 4: XML inside comments */

2008-04-04T19:52:05Z

Proposal 4: XML inside comments

@@ Line 250: / Line 250: @@
    <![endif]-->
 </div>
 </pre>

Eirik: /* Proposal 4: XML inside comments */

2008-04-04T19:09:21Z

Proposal 4: XML inside comments

← Older revision		Revision as of 19:09, 4 April 2008
Line 207:		Line 207:
	* An informative in-line error message should be displayed if non-valid XML is encountered (to help/force authors to behave). The rest of the page should be rendered and not be affected.		* An informative in-line error message should be displayed if non-valid XML is encountered (to help/force authors to behave). The rest of the page should be rendered and not be affected.
	* Legacy browsers will threat the conditional comment as a normal comment, and instead display the (optional) fallback content		* Legacy browsers will threat the conditional comment as a normal comment, and instead display the (optional) fallback content
	* Will not affect ~~existing pages out there~~		* Will not affect legacy content
	* HTML-validators will not report errors because of embedded XML		* HTML-validators will not report errors because of embedded XML

Eirik: /* Reasons why we can't do this */

2008-04-04T18:42:31Z

Reasons why we can't do this

← Older revision		Revision as of 18:42, 4 April 2008
Line 269:		Line 269:
	* Is it "OK" to have real content inside a comment to avoid problems with legacy UAs, even if conforming UAs doesn't "see" it as a comment?		* Is it "OK" to have real content inside a comment to avoid problems with legacy UAs, even if conforming UAs doesn't "see" it as a comment?
	* Is it OK to switch parsing mode mid-document like this (and to effectively require an XML parser in every UA)?		* Is it OK to switch parsing mode mid-document like this (and to effectively require an XML parser in every UA)?
	** Why not? If a UA implements this new syntax, and claims to support ~~say~~ MathML, then of course it needs to be able to parse XML.		** Why not? If a UA implements this new syntax, and claims to support for example MathML or SVG, then of course it needs to be able to parse XML.

Eirik: /* Reasons why we can't do this */

2008-04-04T18:41:47Z

Reasons why we can't do this

← Older revision		Revision as of 18:41, 4 April 2008
Line 269:		Line 269:
	* Is it "OK" to have real content inside a comment to avoid problems with legacy UAs, even if conforming UAs doesn't "see" it as a comment?		* Is it "OK" to have real content inside a comment to avoid problems with legacy UAs, even if conforming UAs doesn't "see" it as a comment?
	* Is it OK to switch parsing mode mid-document like this (and to effectively require an XML parser in every UA)?		* Is it OK to switch parsing mode mid-document like this (and to effectively require an XML parser in every UA)?
			** Why not? If a UA implements this new syntax, and claims to support say MathML, then of course it needs to be able to parse XML.