As far as I know, MapClass is not an official attribute right now, but it is
used to indicate that the class should work in a similar fashion to the Map
class of ECMAScript 6.
Knowing that, I think the specific case of naming conflicts is therefore the
one defined in the ECMAScript 6 Map specification.
-----Message d'origine-----
From: Claudio Saavedra
Sent: Friday, June 14, 2013 5:58 PM
To: www-style@w3.org
Subject: [css-variables] CSSVariablesMap interface doubts
Hi,
I'm implementing the CSSVariablesMap interface in WK. I have a doubt
regarding access to the elements in the map. Previously, if my memory is
not failing me, for a block with a variable declared like
div: {
var-foo: 10px;
}
it was specified that one could access it also as a property of the
interface, directly:
Code Value
el.style.var.get("foo") 10px
el.style.var.foo 10px
Is this direct access still allowed as of the latest specifications? I
think it's not entirely clear.
If the answer is yes, what should the behavior be, shall there be any
variable with a name that conflicts with the methods in the interface?
div {
var-has: 16px;
}
Code Value
el.style.var.has("has") ?
el.style.var.has ?
Also, and slightly unrelated, in 4.2 there's a text "map tuples" with a
hyperlink that seems to be pointing to the wrong place
(http://dev.w3.org/2006/webapi/WebIDL/#REPLACE-ME).
Lastly, I seem not to be able to find where MapClass, the extended
attribute used in the interface definition, is defined. Would someone
care to point me out to it?
Thank you,
Claudio