(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
