TypeError: WeakMap key must be an object, got permanentKey
Categories
(Firefox :: Menus, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox78 | --- | fixed |
People
(Reporter: kernp25, Assigned: Gijs)
References
Details
Attachments
(3 files, 1 obsolete file)
I see this TypeError in console: WeakMap key must be an object, got permanentKey
Comment 1•5 years ago
|
||
Hi kernp25,
I think I need more information here. What version of Firefox are you running? Did you do something immediately before the error showed up? How easy is it for you to reproduce the problem?
(In reply to Mike Conley (:mconley) (:⚙️) from comment #1)
What version of Firefox are you running?
77.0a1 (2020-04-27) (64-Bit)
How easy is it for you to reproduce the problem?
STR:
- Load the attached add-on in about:debugging
- Click on the browser action icon
Assignee | ||
Comment 4•5 years ago
|
||
I can't reproduce with the add-on as attached on nightly from today ... the popup shows an XFO block error (mozilla.org can't be framed), and no output appears in the browser console. Does the iframe loading matter? Am I missing some steps? Does the error only appear if some other prefs are enabled? I doublechecked a second clean profile and there, too, I don't see the error.
I suspect we just need to set group: "browsers",
on the page style actor, but equally, without being able to reproduce it's hard to know if that's really correct or if I'm misunderstanding the problem...
Now uses https://example.com/
(In reply to :Gijs (he/him) from comment #4)
Does the iframe loading matter?
Yes! If the iframe has no src or the src is about:blank then the error will not show.
(In reply to :Gijs (he/him) from comment #4)
I can't reproduce with the add-on as attached on nightly from today ... the popup shows an XFO block error (mozilla.org can't be framed)
The loading in iframe fix has been reverted, so that's why it was not working anymore.
Assignee | ||
Comment 8•5 years ago
|
||
I filed a bug for the generic version of this as bug 1635131, but we can
stop the immediate problem here by just not running this actor except
for tabbrowser browsing contexts.
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Comment 10•5 years ago
|
||
bugherder |
Description
•