Open
Bug 1488357
Opened 7 years ago
Updated 3 years ago
localstorage setitem errors
Categories
(Core :: DOM: Core & HTML, defect, P2)
Tracking
()
UNCONFIRMED
People
(Reporter: vadim.zvf, Unassigned)
Details
Attachments
(1 file)
1.86 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36
Steps to reproduce:
I get errors from prod website.
when i set data to localStorage by localStorage.set.
example in attached file
Actual results:
I get an error without message.
example in attached file
Expected results:
I cant emulate this error on my machine.
user agents from error logs
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0;
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101 Firefox/52.0;
Comment 1•7 years ago
|
||
This doesn't seem like a security issue, and I'm not sure whether this bug presents anything actionable at all.
Group: firefox-core-security
in which cases can an error without message occurred?
(In reply to Johann Hofmann [:johannh] from comment #1)
> This doesn't seem like a security issue, and I'm not sure whether this bug
> presents anything actionable at all.
in which cases can an error without message occurred?
Comment 3•7 years ago
|
||
Hi, I'm unsure if this is the correct component for this issue but I think Core > DOM is a good place to start, please feel free to change the component to a better suited one.
Component: Untriaged → DOM
Product: Firefox → Core
Updated•7 years ago
|
Priority: -- → P2
Comment 5•7 years ago
|
||
It's probably an internal error code that we don't have a detailed message for.
For example, NS_ERROR_DOM_QUOTA_REACHED translates to "Persistent storage maximum size reached", but NS_ERROR_OUT_OF_MEMORY translates to "".
Change error.message to error.name in your logging function and you should be able to see the error code.
Flags: needinfo?(jvarga)
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•