Comments on: Consequences http://john.foliot.ca/consequences/ ...my perspective - without apology Sun, 22 Jan 2012 07:27:46 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jacques Distler http://john.foliot.ca/consequences/comment-page-1/#comment-31 Jacques Distler Wed, 01 Apr 2009 19:05:18 +0000 http://john.foliot.ca/?p=65#comment-31 <blockquote>Or are we to walk away from one of the founding principles of HTML5, that authors deliver confromant code to the browsers?</blockquote> That is not one of the founding principles of HTMLn, at least for any n≤5.€ If wishes were horses, beggars would ride.

Or are we to walk away from one of the founding principles of HTML5, that authors deliver confromant code to the browsers?

That is not one of the founding principles of HTMLn, at least for any n≤5.€

If wishes were horses, beggars would ride.

]]> By: John http://john.foliot.ca/consequences/comment-page-1/#comment-30 John Wed, 01 Apr 2009 17:43:21 +0000 http://john.foliot.ca/?p=65#comment-30 Jacques, you avoid the real question by being so holier-than-thou (while at the same time demonstrating that you can be as much of a jerk as Mark Pilgrim). Point blank - how do you propose that, moving forward, we ensure that developers using the <canvas> element produce conformant HTML5, when the specification insists that fallback content be present? What mechanism do we use to ensure that this happens? Or are we to walk away from one of the founding principles of HTML5, that authors deliver confromant code to the browsers? Your negativity produces zero results - be a man and provide some constructive option to further the discussion, rather than simply deriding me for wanting better than what we have today. Jacques, you avoid the real question by being so holier-than-thou (while at the same time demonstrating that you can be as much of a jerk as Mark Pilgrim). Point blank – how do you propose that, moving forward, we ensure that developers using the <canvas> element produce conformant HTML5, when the specification insists that fallback content be present? What mechanism do we use to ensure that this happens? Or are we to walk away from one of the founding principles of HTML5, that authors deliver confromant code to the browsers?

Your negativity produces zero results – be a man and provide some constructive option to further the discussion, rather than simply deriding me for wanting better than what we have today.

]]> By: Jacques Distler http://john.foliot.ca/consequences/comment-page-1/#comment-29 Jacques Distler Wed, 01 Apr 2009 16:57:46 +0000 http://john.foliot.ca/?p=65#comment-29 WordPress is not capable of producing well-formed XHTML, and no finite number of missives from you to the developers will change that.� More generally, the idea that, if the web is to serve as an application platform, browsers should throw parse errors, just as a C-compiler would, with nonconforming input, is a complete non sequitur. Stick with (as Mark paraphrased) "Screw the sighted people." That, at least, bears some relation to your premise, and is not a complete non sequitur. WordPress is not capable of producing well-formed XHTML, and no finite number of missives from you to the developers will change that.�

More generally, the idea that, if the web is to serve as an application platform, browsers should throw parse errors, just as a C-compiler would, with nonconforming input, is a complete non sequitur.

Stick with (as Mark paraphrased) “Screw the sighted people.” That, at least, bears some relation to your premise, and is not a complete non sequitur.

]]>