"Uncaught DOMException: Operation is not supported" without any details
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
People
(Reporter: pomax, Unassigned)
Details
Attachments
(1 file)
|
16.97 KB,
image/png
|
Details |
{7D160585-A89F-4DF3-AB00-6A678DF5F7F8}.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:123.0) Gecko/20100101 Firefox/123.0
Steps to reproduce:
I have literally no idea. All I know is that at random times during dev work, firefox will throw an "Uncaught DOMException: Operation is not supported" without any additional information, making it impossible to actually track down not just the error, but what even triggers it.
So whatever code is currently throwing that specific error needs a fix that adds both details, and the current call stack.
Expected results:
The error should be accompanied with a description of which operation caused the problem, as well as a call stack.
(to explain why I have no idea: I've enabled and disabled every possible combination of scripts and html tags in the page(s) I'm working on, and maybe 1 in 20 reloads will throw up that error, without any indication that "this is the combination of things that causes it to happen", so I can't even tell if it's my code, if it's something injected by the server, if it's a firefox extension, I just have no idea. At this point, in order to find out how to reproduce it, someone's going to have to first update the actual FF codebase so that the error itself included the necessary details that explain what's even vaguely going wrong, and where)
|
||
Comment 2•1 year ago
|
||
Moving this to Core and waiting for the developer's opinion about it.
If this is not the correct component, please feel free to change it to a more appropriate one. Thanks
|
||
Comment 3•1 year ago
|
||
It looks like this error message is from NS_ERROR_DOM_NOT_SUPPORTED_ERR, which looks like it is used in quite a few places. I'm not sure what the best way is to figure out where this error is coming from.
I would imagine step one to be "start adding details to every one of those throws, fixing one file at a time, until FF no longer throws errors that cannot be traced" =)
It's only 41 files, and that that sounds like a lot, but it'll feel quite a lot easier to manage when it's just a list of 41 sub-tasks and files can be checked off one at a time (and not even necessarily by the same person, of course)
Description
•