Closed
Bug 1102407
Opened 9 years ago
Closed 5 years ago
[e10s] Web Of Trust (WOT) fails to watch dynamic changes, with " TypeError: Argument 1 of MutationObserver.observe does not implement interface Node"
Categories
(WebExtensions :: General, defect)
Tracking
(e10s+)
RESOLVED
INCOMPLETE
Tracking | Status | |
---|---|---|
e10s | + | --- |
People
(Reporter: dholbert, Unassigned, NeedInfo)
References
()
Details
(Whiteboard: [amo-author-notified] triaged)
Attachments
(1 file)
27.96 KB,
application/javascript
|
Details |
STR: 0. Be using e10s (currently on by default in Nightly) 1. Install Web of Trust extension from https://addons.mozilla.org/en-US/firefox/addon/wot-safe-browsing-tool/ 2. Log into Facebook. 3. Inspect your terminal. (I'm assuming you started Firefox from the terminal & can see its terminal output) ACTUAL RESULTS: This appears in your terminal. wot_search.watch: failed with TypeError: Argument 1 of MutationObserver.observe does not implement interface Node. Basically, WOT registers a mutation observer so it can scan the URLs of new links that appear dynamically on your timeline (and label them as safe/unsafe). But it seems to be failing to hook up the mutation observer, in e10s mode.
Reporter | ||
Comment 1•9 years ago
|
||
Also, FWIW: WOT is a "Featured" add-on on AMO, with nearly 1.3 million users. It's our 9th-most-popular extension, according to https://addons.mozilla.org/en-US/firefox/extensions/?sort=users The current WOT version on AMO is 20131118 (released on 2013-11-18, just over a year ago). So, not too surprising that it doesn't quite work with e10s. We should probably reach out to them to let them know about this bug, with recommended workarounds for setting up a mutationobserver in e10s builds. [--> CC'ing the two bugzilla users who have "mywot.com" email addresses.]
Blocks: e10s-addons
Reporter | ||
Comment 2•9 years ago
|
||
Reporter | ||
Comment 3•9 years ago
|
||
FWIW, if I add logging to print out the thing we're passing to 'observe', I get this in non-e10s mode: > Calling observe with content: [object HTMLDocument] but I get this in non-e10s mode: > Calling observe with content: [object CPOW [object HTMLDocument]]
Comment 4•9 years ago
|
||
The WOT add-on was reported as working in bug 1002880, so this might be a recent regression.
Blocks: 1002880
Updated•9 years ago
|
tracking-e10s:
--- → +
Reporter | ||
Comment 5•9 years ago
|
||
(In reply to Chris Peterson (:cpeterson) from comment #4) > The WOT add-on was reported as working in bug 1002880, so this might be a > recent regression. I don't think so -- note that the only thing broken here is the mutation observer (and you can only tell by watching your terminal, or perhaps by noticing un-WOT-annotated links show up on Facebook). I'll bet we just didn't notice that the mutation observer stuff was broken over in bug 1002880.
Reporter | ||
Comment 6•9 years ago
|
||
Note that this error-message doesn't seem to show up in my browser console -- only in my terminal (via stdout). So, it would've been easy to miss. Also: as you might expect, I can confirm that WOT is failing to annotate links in dynamically-loaded chunks of Facebook, when e10s is enabled (presumably due to the observe() call in this bug). So for example, I see green/orange/red WOT icons next to links that are shown in my initial Facebook load, but if I scroll to the bottom to pull in more content, then *that* content doesn't have WOT icons next to its links.
Updated•8 years ago
|
tracking-e10s:
+ → ---
Whiteboard: [amo-author-notified]
Updated•8 years ago
|
tracking-e10s:
--- → +
Updated•7 years ago
|
Flags: needinfo?(sescalante)
Updated•7 years ago
|
Flags: needinfo?(sescalante)
Whiteboard: [amo-author-notified] → [amo-author-notified] triaged
Comment 8•5 years ago
|
||
With Firefox 57 only WebExtensions are permitted and are, by default, e10s compatible.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
Assignee | ||
Updated•4 years ago
|
Component: Add-ons → General
Product: Tech Evangelism → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•