Re: [cssom] Remove setPropertyValue and setPropertyPriority?

On Thu, Oct 2, 2014 at 4:03 AM, Simon Pieters <simonp@opera.com> wrote:
> Since setPropertyValue and setPropertyPriority were added as a compromise
> solution when the behavior of setProperty was discussed last year[1], and
> setProperty has now changed to match Firefox[2], should we remove
> setPropertyValue and setPropertyPriority? I think they haven't been
> implemented anywhere.
>
> [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=23066#c5
> [2] https://www.w3.org/Bugs/Public/show_bug.cgi?id=23066#c8

Yeah, I don't think we need them then.

~TJ

Received on Thursday, 2 October 2014 18:54:27 UTC