W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2015

Re: [whatwg] Case-sensitivity of CSS type selectors in HTML

From: Anne van Kesteren <annevk@annevk.nl>
Date: Fri, 8 May 2015 07:42:36 +0200
Message-ID: <CADnb78i_dkRK3z0xOeGir7RupN=FZnbzrE-DqSg1HWez6pLGaQ@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: WHATWG <whatwg@lists.whatwg.org>, Boris Zbarsky <bzbarsky@mit.edu>, Elliott Sprehn <esprehn@chromium.org>, Rune Lillesveen <rune@opera.com>
On Thu, May 7, 2015 at 11:23 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> Well, beyond the existing conflicts of <style>, <script>, and <a>.
> (<font> too, but that's dropped from SVG2, so who cares.)

<textArea> is out too?

With respect to case-insensitive matching, I don't really understand
why we simultaneously want to make these rather trivial changes to SVG
while at the same time move to constructors for creating elements,
which is even stricter than createElementNS() (literal has to be
correctly spelled or you get an exception). If we want to move to a
world where people write

  new SVGRectElement

why would we even bother making

  document.createElement("RECT")

work?

Same for CSS, the majority of CSS already uses type selectors where
the case matches up with the HTML. Is complicating it really worth it?
We should bring the languages closer, but we shouldn't put the
mistakes we made with HTML into SVG.


-- 
https://annevankesteren.nl/
Received on Friday, 8 May 2015 05:43:02 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:31 UTC