W3C home > Mailing lists > Public > www-style@w3.org > May 2013

Re: [cssom] Proposal for obtaining robust style information via Javascript - getStyle()

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 8 May 2013 09:21:28 -0700
Message-ID: <CAAWBYDAEPyUKBGTrHrUPfMDBh8O2YRygyX-hZP+70tdEJwuOGg@mail.gmail.com>
To: Simon Pieters <simonp@opera.com>
Cc: "www-style@w3.org" <www-style@w3.org>, Mike Sherov <mike.sherov@gmail.com>
On Wed, May 8, 2013 at 4:26 AM, Simon Pieters <simonp@opera.com> wrote:
> On Tue, 07 May 2013 23:56:58 +0200, Tab Atkins Jr. <jackalmage@gmail.com>
> wrote:
>>> That sounds reasonable, but I still want use cases stated for everything
>>> new
>>> introduced so we don't end up specifying and implementing things that
>>> don't
>>> get used.
>> Well, people currently get value out of getComputedStyle(), and it
>> only returns used styles for a handful of properties, returning
>> computed for everything else, including those that are roughly similar
>> to the legacy-used-value properties.  That suggests that computed
>> values are valuable to authors.  If we're going to introduce some new
>> getters in the style that dbaron suggests, it would be worthwhile to
>> have computed styles align with that.
> I've now added David's suggested API (except pseudoStyle() is called
> pseudo()) and changed getDefaultComputedStyle(element) to
> element.defaultStyle.
> https://dvcs.w3.org/hg/csswg/rev/7e12087e6188


I don't see that PseudoElement implements GetStyleUtils anywhere in
the document, though it's in the idl.

Received on Wednesday, 8 May 2013 16:22:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:29 UTC