Strict mode warning dumped to stdout.
We're doing developer tool prioritization, filter on 'brontozaur'
to ignore the spam.
I am not able to reproduce this. Richard, what do we need to do to reproduce this bug?
(In reply to Michael Ratcliffe from comment #2)
> I am not able to reproduce this. Richard, what do we need to do to reproduce
> this bug?
As I recall, this was just launching an m-c build with a testing profile. I periodically scan through the console output and file bugs for all the warnings and errors I find.
I can't reproduce this bug in a current build, but that doesn't mean it isn't still lurking. I assume this is the culprit:
A little bit of code reading might reveal a timing bug here.
Created attachment 583429 [details] [diff] [review]
Ridiculously simple patch
Ridiculously simple patch.
inputEventHandler() could theoretically be called before setInputValue(). Defining this.lastInputValue as "" fixes this.