W3C home > Mailing lists > Public > www-svg@w3.org > December 2013

Re: Relaxing SVGList* item object equality in Blink/Chromium

From: Robert O'Callahan <robert@ocallahan.org>
Date: Thu, 12 Dec 2013 15:47:07 +1300
Message-ID: <CAOp6jLZRuH8W=kCJ=2mJMmhAcA-TVd_PkKWHRU5BErV55EaN2w@mail.gmail.com>
To: Kouhei Ueno <kouhei@google.com>
Cc: www-svg <www-svg@w3.org>
On Thu, Dec 12, 2013 at 2:58 PM, Kouhei Ueno <kouhei@google.com> wrote:

> 2013/12/12 Robert O'Callahan <robert@ocallahan.org>:
> > For example, does this mean svgElement.x !== svgElement.x? Or
> > svgElement.x.baseVal != svgElement.x.baseVal?
> I want to drop guarantees about svgElement.x === svgElement.x, and
> svgElement.x.baseVal === svgElement.x.baseVal. They may ===, but it
> may not be all the time.

That's bad. A basic principle of Web APIs is that DOM attribute getters
consistently return the same object unless the author does something to
explicitly change them. See
the rest of that thread.

I think instead of just saying you'll violate the spec in some
not-very-well-defined ways, you really should propose a spec change that
puts the spec into a state Blink will comply with. That will help everyone
understand the impact of what you're proposing to do.

We did a lot of work in Gecko a few years ago so we could comply with the
spec without creating the implementation issues discussed in the blink-dev
thread, and I think we did a pretty good job since we haven't had those
issues since. So it is possible.

Jtehsauts  tshaei dS,o n" Wohfy  Mdaon  yhoaus  eanuttehrotraiitny  eovni
le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o  Whhei csha iids  teoa
stiheer :p atroa lsyazye,d  'mYaonu,r  "sGients  uapr,e  tfaokreg iyvoeunr,
'm aotr  atnod  sgaoy ,h o'mGee.t"  uTph eann dt hwea lmka'n?  gBoutt  uIp
waanndt  wyeonut  thoo mken.o w
Received on Thursday, 12 December 2013 02:47:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:54:49 UTC