Consider dispatching the input event for text inputs and textareas asynchronously

NEW
Unassigned

Status

()

Core
DOM
4 years ago
4 years ago

People

(Reporter: Away for a while, Unassigned)

Tracking

Trunk
x86
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
I tried doing that as part of bug 675579 but that breaks a lot of tests and might have web compat risk.
(Reporter)

Updated

4 years ago
Blocks: 675579
(Reporter)

Comment 1

4 years ago
I looked and it seems to me like WebKit/Blink agree on our behavior.
1. I do not see how this is meant to help bug 675579 - or that it needs help to begin with.
2. I think that making the input event asynchronous would be a very real backward compatibility risk.

So, IMHO, don't do this.
(Reporter)

Comment 3

4 years ago
(In reply to comment #2)
> 1. I do not see how this is meant to help bug 675579 - or that it needs help to
> begin with.

It shouldn't affect that bug.

> 2. I think that making the input event asynchronous would be a very real
> backward compatibility risk.

I agree.  Do you think it's worth proposing the spec to be fixed here?  I chatted with Hixie about this on IRC briefly but we didn't get to a conclusion.
I did not realize the spec says it is supposed to be asynch. If there is lack of interop, it's always worth discussing it. But I don't know enough about it to participate actively.
You need to log in before you can comment on or make changes to this bug.