onChange, onEditorReady events not firing on Firefox with version 0.2.0
See original GitHub issueAfter upgrading to 0.2.0, I get the following error from the component that uses Trix:
Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object. Check the render method of `TextAreaInput`.
I can’t tell what has changed in react-trix or trix itself that might trigger this error; the usage seems to correspond to the examples pretty closely:
Issue Analytics
- State:
- Created 6 years ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
The change event is not firing when bound to a input text field ...
Using FireFox 15.0.1: In the following code the "onChange" event does not fire with the tab key, but will fire when the mouse...
Read more >onchange event on input type=range is not triggering in ...
The demo shows the range/slider value as well as the number of times the standard "change" , "input" and custom "onRangeChange" events have...
Read more >Debugger for Firefox - Visual Studio Marketplace
A VS Code extension to debug web applications and extensions running in the Mozilla Firefox browser. Install from VS Code Marketplace.
Read more >In Firefox Click Event Does Not Fire After On-change On Input ...
Oracle Application Express (APEX) - Version 4.2.3.00.08 and later: In Firefox Click Event Does Not Fire After On-change On Input Field.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is now fixed in 4028d89ee845e48c28e7eeab74d118c83f23ab05 a new NPM package was published 0.2.1.
Thank you for reporting this, highly appreciated.
That’s good, thank you very much for your patience. I will investigate Firefox (should have had done that frankly), lesson learned. I’ll keep you posted when I have the update ready.