Re: [cssom] overwriting an important style

To close the loop here, Zack and Simon, we just resolved on the telecon to
change behavior to match Firefox here. Thanks everyone, especially Rossen,
for researching potential backCompat issues.

On Fri, Sep 12, 2014 at 5:09 PM, Mike Sherov <mike.sherov@gmail.com> wrote:

>
>
> On Tue, Sep 9, 2014 at 8:38 PM, Zack Weinberg <zackw@panix.com> wrote:
>
>> On Tue, Sep 9, 2014 at 6:11 AM, Mike Sherov <mike.sherov@gmail.com>
>> wrote:
>> > On Tue, Sep 9, 2014 at 05:22 AM, L. David Baron<dbaron@dbaron.org>,
>> wrote:
>> >> On Monday 2014-09-08 09:32 +0200, Simon Pieters wrote:
>> >> > >Can this be changed?
>> >> >
>> >> > If you can convince David Baron... :-)
>> >>
>> >> So I do like it the way it is, but I don't think I'm the major
>> >> obstacle. I thought that Gecko was the only browser that does it
>> >> the way you want (thanks to Zack's change a number of years ago),
>> >> and all the others match my understanding. Are those other browsers
>> >> willing to change? (Or is my memory wrong?)
>> >
>> > FF is the only browser that doesn't match spec here and does what I
>> want.
>> > The jQuery team opened bugs for this against WebKit, Blink, and IE.
>>
>> The last time this came up, didn't someone do a survey of all the JS
>> code on Github or something like that, and find that nearly all code
>> that uses this API assumed it worked the way it does in Firefox right
>> now?  That seems like a pretty compelling argument for changing the
>> spec all by itself, if you ask me.
>>
>
> So where do we go from here? I'll say again, I'm fairly certain a few
> browsers would be happy to address this bug if we can agree it is one and
> address this in the spec.
>
>
>>
>> zw
>>
>
>
>
> --
> Mike Sherov
>
>


-- 
Mike Sherov