Reporter: Breaks when using BitWarden
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Low
|
Unassigned | ||
3.11 |
Fix Released
|
Low
|
Unassigned |
Bug Description
Howdy.
I've been having issues where when I open the Reporter, I get a white screen. I noticed in the Console, I get the following error:
Uncaught SyntaxError: Invalid left-hand side in assignment. This error references oils_rpt_
Here is the code causing the issue:
/* scours the doc for elements with IDs. When it finds one,
it grabs the dom node and sets a reference to the node at DOM[id]; */
function oilsRptIdObject
if(!node) node = document.
if( node.nodeType != 1 ) return;
var id = node.getAttribu
if( id ) eval("DOM.
var children = node.childNodes;
for( var c = 0; c < children.length; c++ )
oilsRptIdObje
}
Adding some debugging stops to this, I found it was failing at a node when id resolved as "bw-fido2-
https:/
https:/
While there seems to be grumbling elsewhere online about Bitwarden injecting this, it doesn't seem like that's going to change given that increasingly Google and Microsoft are pushing passkeys.
This code seems like it could use improvement as there's something off here - (why are we creating DOM.foo style getters? Why is it looking for anything with an id field when getElementById exists?
Anyway, hoping just "this will get rewritten in Angular" is the solution here, but at the same time thought I'd report it in case anyone else hits this issue. I'm guessing other password managers or extensions may have similar issues as well.
Changed in evergreen: | |
status: | New → Confirmed |
importance: | Undecided → Low |
tags: | added: signedoff |
Changed in evergreen: | |
milestone: | none → 3.12.3 |
Changed in evergreen: | |
assignee: | Terran McCanna (tmccanna) → nobody |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
The good news is that bug 1993823 is coming along so you're right about that being the real fix. The point about DOM.whatevs is a good one, I wonder if that was leftover from the XUL days or something, ick.
This bug probably shouldn't be marked invalid or won't fix or anything like until the Angular reporter is available that so that people can find this bug in case they run into it; thanks for tracking this down James!