esp...@chromium.org
unread,May 1, 2015, 1:47:03 AM5/1/15Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to ru...@opera.com, p...@chromium.org, tim...@chromium.org, alexis...@intel.com, apavlo...@chromium.org, blink-...@chromium.org, blink-re...@chromium.org, blink-re...@chromium.org, dglazko...@chromium.org, eae+bli...@chromium.org, ed+bli...@opera.com, rob....@samsung.com, sigb...@opera.com
On 2015/04/30 at 11:20:39, rune wrote:
> On 2015/04/30 01:04:42, esprehn wrote:
> > On 2015/04/29 at 10:43:07, rune wrote:
> > > ping
> >
> > I talked to tab about this, why not just treat SVG case insensitively
always?
> I don't know the rationale for the way it's spec'ed. Hixie would know, I
guess. I found some very long posts on the whatwg list, but not able to
find a
definitive answer. What's really weird is the inconsistency between
case-insensitivity of tag names in the source and the case-sensitivity of
the
selector against the camelCased form the tags names are transformed into.
I talked to Tab about this more today, I think the agreement is to just make
selectors always match everything case insensitively. So we'd change
matchesTagName to have a check for isHTMLElement() and do what it does now,
and
another case where it does a case insensitive compare of the localName (and
namespace?)
https://codereview.chromium.org/1099963003/