Editor.js:75 Uncaught Error: Expected target ref
See original GitHub issueHello, I keep getting this error on initializing:
This is the row which is getting the error from the library:
var target = _this.elementRef.current;
Here is my Editor component:
<Editor
apiKey="apiKey"
inline
init={{
menubar: false,
toolbar: false
}}
onEditorChange={setEditorState}
value={editorState}
/>
initialValue is passed after data fetch in the same component with useEffect lifecycle hook. I am not sure if I am missing something that I should add as props. Did anybody else had the same issue?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Pytorch ValueError: Expected target size (2, 13), got torch.Size ...
The error message was kind of misleading since it said that the target was the wrong shape, when really the output was the...
Read more >cannot read properties of undefined (reading 'publish')
The error states that node.pubsub is undefined while you are trying to access the publish property on the object. Quickly reading through an...
Read more >478389 - Long data: URLs don't work on iframes for PDFs
The expected result would be to see the generated pdf with the picture. ... pdf.js:75 Uncaught (in promise) TypeError: Cannot read property ......
Read more >Buster.JS Documentation - Read the Docs
JS exposes four global variables: buster, expect, assert, and refute. ... Uncaught errors are errors that the test runner is unable to ...
Read more >Untitled
X30cr14, Stevens creek acura, Lispersteenweg 237, Olympic archery target distance, ... Izrada kisobrana, Lazarus 1991 reference, Billy stokes knoxville, ...
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
Confirmed, fixed in 3.8.1 🎉 Thanks for the quick fix!
I started experiencing the same error after upgrading from 3.7.0 to 3.8.0.