W3C home > Mailing lists > Public > public-evangelist@w3.org > July 2004

Safari and proprietary "contenteditable" attribute

From: Karl Dubost <karl@w3.org>
Date: Mon, 5 Jul 2004 10:32:11 -0400
Message-Id: <19FF39EA-CE90-11D8-8E1E-000A95718F82@w3.org>
To: public-evangelist@w3.org
I'm pretty sure, many of you, are already reading the Dave Hyatt's  
weblog, one of the Safari developer.

*It seems*, they have decided to implement the "contenteditable"  
attribute [1] in WebCore [2] (WebCore is the rendering engine that  
Safari is using for handling Web pages.)

	"""The new WebCore also supports HTML editing.
	You can specify editable regions in a page
	using the contenteditable attribute (which
	maps to a CSS property behind the scenes,
	so you can even set that property in your user
	stylesheets if you want to get crazy)."""

... more than implementing the XHTML 2.0 attribute... [3]

Though there might be a problem with that:

	- contenteditable is a microsoft attribute, not in W3C specs
	- a module already exists in XHTML 2.0 WD to achieve the same effect
	- if implemented correctly let's say in its proper namespace, it means  
that
		1. people will have to write safari:contenteditable=""
		2. people will not be anymore to have valid Web pages.



[1]  
http://msdn.microsoft.com/workshop/author/dhtml/reference/properties/ 
contenteditable.asp
[2] http://weblogs.mozillazine.org/hyatt/archives/2004_07.html#005905
[3]  
http://www.w3.org/TR/2003/WD-xhtml2-20030506/mod-attribute- 
collections.html#col_Edit


-- 
Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager
*** Be Strict To Be Cool ***

Received on Monday, 5 July 2004 10:32:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 15 July 2011 00:13:22 GMT