spark
14 April 2023 11:14
1
Windows 10 22H2, Firefox 112, Joplin 2.9.17.
Clicking on the web clipper icon doesn't display the clipper dialogue box, as shown here:
You can see the very top of the dialogue if you look closely.
It has been working up until a Windows update and a Firefox update, although I cannot remember if the clipper stopped working immediately after either of these updates. I have disabled all other Firefox addons, restarted the browser, restarted the laptop, restarted Joplin and disabled/re-enabled the clipper addon, all to no effect. It seems a strange problem and I wondered if anyone else had encountered it and hopefully found a solution.
Is this the similar bug as this one?
opened 05:16PM - 12 Apr 23 UTC
bug
<!--
Please provide a clear and concise description of what the bug is. (In t… he section Steps To Reproduce.)
Include screenshots for UI problems if needed.
DO NOT create screenshots of text !!! Copy and paste the text into a code block.
Please test using the latest Joplin release to make sure your issue has not already been fixed.
-->
When setting `user_pref("privacy.resistFingerprinting", true);` in `user.js`, the Web Clipper extension cannot be opened. When clicked on, it only shows a thin sliver of UI, like this:
This is not dependent on the currently viewed webpage. Other extensions such as KeePass-XC-Browser (also pictured) do not have a similar problem.
<!--
IMPORTANT: If you are reporting a clipper bug, please include an example URL that shows the issue.
Without the URL the issue is likely to be closed.
-->
## Environment
Joplin version: Joplin 2.9.17 (prod, win32)
Sync Version: 3
Profile Version: 41
Keychain Supported: Yes
Revision: a84a8e7
Web Clipper version: 2.11.2
Platform: Windows
OS specifics: Windows 10, Firefox: 112.0 (64-bit)
<!--
Platform can be one of: macOS, Linux, Windows, Android, iOS, terminal (or a combination)
OS specifics: e.g. OS version, Linux distribution, Android/iOS version...
-->
## Steps to reproduce
1. Set `user_pref("privacy.resistFingerprinting", true);` in `user.js`.
2. Relaunch Firefox.
3. Click on the Joplin Web Clipper extension.
<!--
Issues without reproduction steps are likely to stall.
-->
## Describe what you expected to happen
I would expect the extension to first ask me for authorization (the desktop app still registers the request and I granted the authorization, see log below) and on subsequent clicks show the Web Clipper UI.
## Logfile
```js
17:04:57.337 Popup: Init bridge and restore state... index.js:113:9
17:04:57.339 Popup: Init bridge bridge.js:21:10
17:04:57.343 Popup: Env: prod bridge.js:84:10
17:04:57.344 Popup: Creating React app... index.js:117:9
17:04:57.347 findClipperServerPort: Trying 41184 bridge.js:256:12
17:04:57.363 findClipperServerPort: Got response: JoplinClipperServer bridge.js:259:12
17:04:57.379 Popup: Restoring saved state:
Object { authToken: "", authTokenTimestamp: 0, selectedFolderId: null, token: "d6a57bb137ebd9adf2f42d249092d03dfb22663d5a8439e72cd115d453fab42e5b1234d74f7a6d95d35466ef845c6fab496f9b793e2ac8411c50683b0cb62796" }
bridge.js:244:10
17:04:57.381 Popup: GET auth/check bridge.js:400:10
17:04:57.392 checkAuth: we already have a valid token - exiting bridge.js:134:11
17:04:57.394 Popup: GET folders bridge.js:400:10
17:04:57.410 Popup: GET tags bridge.js:400:10
17:04:57.424 Sending message
Object { name: "isProbablyReaderable" }
bridge.js:394:10
17:04:57.435 Popup: Got command:
Object { name: "isProbablyReaderable", value: true }
bridge.js:47:11
17:05:11.557 Popup: Init bridge and restore state... index.js:113:9
17:05:11.559 Popup: Init bridge bridge.js:21:10
17:05:11.561 Popup: Env: prod bridge.js:84:10
17:05:11.562 Popup: Creating React app... index.js:117:9
17:05:11.563 findClipperServerPort: Trying 41184 bridge.js:256:12
17:05:11.572 findClipperServerPort: Got response: JoplinClipperServer bridge.js:259:12
17:05:11.597 Popup: Restoring saved state:
Object { authToken: "", authTokenTimestamp: 0, selectedFolderId: null, token: "d6a57bb137ebd9adf2f42d249092d03dfb22663d5a8439e72cd115d453fab42e5b1234d74f7a6d95d35466ef845c6fab496f9b793e2ac8411c50683b0cb62796" }
bridge.js:244:10
17:05:11.600 Popup: GET auth/check bridge.js:400:10
17:05:11.602 Sending message
Object { name: "isProbablyReaderable" }
bridge.js:394:10
17:05:11.606 checkAuth: we already have a valid token - exiting bridge.js:134:11
17:05:11.611 Popup: GET folders bridge.js:400:10
17:05:11.616 Popup: Got command:
Object { name: "isProbablyReaderable", value: true }
bridge.js:47:11
17:05:11.634 Popup: GET tags bridge.js:400:10
17:05:11.712 Popup: Saving state
Object { selectedFolderId: null }
bridge.js:236:11
```
<!--
Please attach a debug log. Issues without a debug log are likely to stall.
For information on how to collect a log file: https://joplinapp.org/debugging/
-->
spark
14 April 2023 14:06
3
Brilliant, that's exactly it, thank you. Setting privacy.resistFingerprinting to false makes the web clipper dialogue visible again.
Looks like I'm suffering the same issue... Can anyone tell where's the user.js file the post is talking about? Is this a Firefox or Joplin settings file?
Thanks in advance for any help!
It's Firefox, but I believe that you would have had to have manually switched this setting on for it to be a problem.
Anyway, to check type about:config in the URL bar at the top of the Firefox browser and press enter. Acknowledge the warning. Search for privacy.resistFingerprintingfalse . The two-way arrow to the right will let you flip the value if needed.
spark
17 April 2023 10:15
7
EDIT: Beaten to it by dpoulton! See screenshot below:
1 Like
dpoulton:
resistFingerprinting
Thanks guys! The value is already set to "false", so what could I do now? In my case, the web clipper only displays "Connecting to the Joplin application" forever. I've already checked that the clipper is activated in Joplin, but its status is "idle". Could it be that Firefox plugin doesn't communicate on the right port? If yes, how can I check this?
I was going to post a link to another thread about a similar problem and then realised that it was your post
It's possibly better to carry on with your own thread rather than here, which relates to a different problem.
OK, sorry for the cross-post but I'm investigating any solution I can find! Will resume the other thread then but should you have any hint for this, please tell me!
1 Like
system
18 May 2023 07:51
11
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
