Re: [selectors-api] Consider backporting find() behavior to querySelector() from Kang-Hao (Kenny) Lu on 2012-06-18 (public-webapps@w3.org from April to June 2012)

From: Kang-Hao (Kenny) Lu <kennyluck@csail.mit.edu>
Date: Mon, 18 Jun 2012 22:57:17 +0800
To: Simon Pieters <simonp@opera.com>
CC: "public-webapps.w3.org" <public-webapps@w3.org>
Message-ID: <4FDF41CD.2080706@csail.mit.edu>

(12/06/18 22:45), Simon Pieters wrote:
> I think we should instead either fix the old API (if it turns out to not
> Break the Web) or live with past mistake (if it turns out it does). To
> find out whether it Breaks the Web (and the breakage can't be evanged),
> I suggest we ship the backwards-incompatible change to querySelector()
> in nightly/aurora (or equivalent) in one or more browsers for some time.

I didn't read through all the QSA threads, but isn't the function name
itself a mistake that many people don't want to live with?

I'd rather like to see querySelector() marked as "deprecated" so it
doesn't appear in tutorials in the future.

Cheers,
Kenny

Received on Monday, 18 June 2012 14:57:45 UTC