🐛 [BUG]: Uncaught TypeError: Cannot read properties of undefined (reading 'toLowerCase')
tpoxa opened this issue · comments
Is there an existing issue for this?
- I have searched the existing issues and this is a new bug.
Current Behavior
I haven't updated for a while, so I did and noticed I have a bunch of errors when I select the node.
The come from this function
function isKeyMatch(pt, _t, xt, kt) {
const Ct = _t.split("+").map(Et=>Et.trim().toLowerCase());
return Ct.length === 1 ? pt.toLowerCase() === _t.toLowerCase() : (kt ? xt.delete(pt.toLowerCase()) : xt.add(pt.toLowerCase()),
Ct.every((Et,$t)=>xt.has(Et) && Array.from(xt.values())[$t] === Ct[$t]))
}Expected Behavior
No errors
Steps To Reproduce
It looks like this error is specific to my setup. If a nature of the error is completely not clear I'll try to provide some access to that page online. Is that going to help?
Relevant log output
No response
Anything else?
When does this issue happen exactly? Does it actually happen when you do some keypress combo?
If you're using some keypress combo, what does it look like? Can you show me some of the code you use? :)
@bcakmakoglu just clicking on element, no keys pressed, that's very odd
Selecting as in clicking a node or as in creating a selection-box? Just clicking a node doesn't seem to trigger the isKeyMatch function 🤔
Which version are you on right now?
Any more infos in the stacktrace? Like a hint where the error started from so that it ended up in the isKeyMatch section?
Does this happen across all browsers or just specific ones?
ok, thanks for the tip, it happens only in Chrome. When I try incognito mode the error is not occurring even in chrome, so checking extensions
Any updates on this? Were you able to find the issue?
Any updates on this? Were you able to find the issue?
unfortunately I could not reproduce the issue, turning off extensions did not help
Are you, by any chance, using any key-filters for any key-codes that might be empty arrays?
Fixed in 1.29.2
fixed indeed, thanks @bcakmakoglu