After todays teleconf, we have four candidates for renaming the widget
element's id attribute:
* widgetid
* uid
* wid
* name
My preference is uid, which is what I have put in the spec for now.
I don't like widgetid, because it looks weird name to widget widgetid=blabla
I don't like wid, because wid doesn't mean much to me.
I don't like name, because it would mean renaming the name element
to title (which goes against every widget user agent already using
name as we have specified it)
I like uid, because it implied unique id to me.
Kind regards,
Marcos
On Mon, Oct 27, 2008 at 4:32 PM, Marcos Caceres
[EMAIL PROTECTED] wrote:
HI All,
After discussions on IRC, it has become clear that we need to rename
the widget element's id attribute:
[17:24] Hixie the real question is not what allowed values it has,
but whether it should be used for CSS #id matching or DOM
getElementById() matching
[17:24] Hixie if it shouldn't, then don't call it id=
[17:24] Hixie if it shoul, do
[17:24] tlr-off or for any other matching-by-id, that is
[17:24] tlr-off indeed
[17:25] tlr-off e.g., xpath
We don't use widget id in the manner above. Any suggestions?
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
--
Marcos Caceres
http://datadriven.com.au
