W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2008

Re: [widgets] id attribute rename

From: Marcos Caceres <marcosscaceres@gmail.com>
Date: Thu, 30 Oct 2008 13:52:12 +0000
Message-ID: <b21a10670810300652s32ff7dabhba9b5851ae116356@mail.gmail.com>
To: public-webapps <public-webapps@w3.org>

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,

On Mon, Oct 27, 2008 at 4:32 PM, Marcos Caceres
<marcosscaceres@gmail.com> 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
Received on Thursday, 30 October 2008 13:52:56 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:12 UTC