On Thu, Mar 10, 2016 at 2:24 AM, Gary Kacmarcik (Кошмарчик) <
gary...@chromium.org> wrote:
> On Wed, Mar 9, 2016 at 3:40 PM, Hallvord Reiar Michaelsen Steen <
> hst...@mozilla.com> wrote:
>
>>
>> On Wed, Mar 9, 2016 at 11:19 PM, Gary Kacmarcik (Кошмарчик)
>> wrote:
>>
>> > There is a design tensi
On Thu, Mar 10, 2016 at 12:40 AM, Hallvord Reiar Michaelsen Steen <
hst...@mozilla.com> wrote:
> > Just using mutation observers, one can see the change that was made, but
> > doesn't really know what the user's intentions were, right?
>
> I guess so, haven't used them for anything. Perhaps the "a
On Wed, Mar 9, 2016 at 3:40 PM, Hallvord Reiar Michaelsen Steen <
hst...@mozilla.com> wrote:
>
> On Wed, Mar 9, 2016 at 11:19 PM, Gary Kacmarcik (Кошмарчик)
> wrote:
>
> > There is a design tension between the 2 extreme approaches, each with
> pros
> > and cons:
> >
> > (1) A single 'beforeinput'
> Just using mutation observers, one can see the change that was made, but
> doesn't really know what the user's intentions were, right?
I guess so, haven't used them for anything. Perhaps the "after the
fact" nature was a design flaw in Mutation Observers.
> The browser meeting also came up with
On Wed, Mar 9, 2016 at 5:29 AM, Hallvord Reiar Michaelsen Steen <
hst...@mozilla.com> wrote:
> On Mon, Mar 7, 2016 at 11:00 PM, Gary Kacmarcik (Кошмарчик)
> wrote:
>
> > Agreed. That is the major benefit of 'beforeinput' and 'input' -- you
> will
> > receive a 'beforeinput' event just before any
On Wed, Mar 9, 2016 at 2:29 PM, Hallvord Reiar Michaelsen Steen <
hst...@mozilla.com> wrote:
> On Mon, Mar 7, 2016 at 11:00 PM, Gary Kacmarcik (Кошмарчик)
> wrote:
>
> > Agreed. That is the major benefit of 'beforeinput' and 'input' -- you
> will
> > receive a 'beforeinput' event just before any
On Wed, Mar 9, 2016 at 2:29 PM, Hallvord Reiar Michaelsen Steen
wrote:
> In my personal (and humble) opinion it's not actually a benefit for
> developers to have only one event that will fire a lot and indicate
> lots of different things. I accept that library authors want a
> convenient "point of
On Mon, Mar 7, 2016 at 11:00 PM, Gary Kacmarcik (Кошмарчик)
wrote:
> Agreed. That is the major benefit of 'beforeinput' and 'input' -- you will
> receive a 'beforeinput' event just before any DOM update (with an option to
> cancel it), and you'll also receive an 'input' event just after the DOM w