mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #54] Duplicates on firefox #52
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#52
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mobamoba on GitHub (Mar 18, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/54
I'm using the 2.0.0. installed from AMO. In the debugging log, I get the following error over and over:
Error: Could not establish connection. Receiving end does not exist.
Chrome extension has no problem connecting to the exact same server. Also, with Firefox, clicking "Add Account" does nothing for a while after initial install - I had to click it 6 or so times after initial install in order to get the account window to finally show.
Let me know if there's anything additional that would help you debug. Thanks.
@marcelklehr commented on GitHub (Mar 18, 2018):
Hey @mobamoba
Thank you for reporting this :) The source of the error message appears to be unrelated to your server but involves internal message passing between addon parts. It might also be completely unrelated.
Could you tell me your version of firefox?
@mobamoba commented on GitHub (Mar 18, 2018):
59.01. What's odd is that it says it completed successfully (in the debug console) but then never really stops and just gives repeats of that same error and then continuously eats CPU.
@marcelklehr commented on GitHub (Mar 18, 2018):
Did you create a new account? Did you select the root bookmarks folder in your browser or a sub folder?
@mobamoba commented on GitHub (Mar 18, 2018):
Yes. And unfortunately, in addition to the message I noted above, the extension also kept creating a bunch of dupes.
@marcelklehr commented on GitHub (Mar 18, 2018):
Then I recommend resetting the custom folder and letting it create a new one for you, so you can see what is going on and sort it out. When using the root folder for syncing, bookmarks that have been placed in the root folder are not visible in your browser! So, when you see what's going on in a separate dedicated floccus folder, I recommend saving all bookmarks that are only in the dedicated folder to some other location and then deleting everything in the folder, so you have a clean slate.
What do you mean by "it created dupes"? You had the same bookmarks in your browser and on the server and they weren't deduped? Or did it create duplicates out of the blue?
@mobamoba commented on GitHub (Mar 18, 2018):
It created dupes out of the blue then threw dupe errors. These dupes weren't present before - they were created by the extension.
I'll try what you recommended but, because of the dupes, my original 700 bookmarks have now blossomed to around 2000 on my Nextcloud server and there's no easy way that I can see to bulk delete them. Do you know how to do that? Because if so, I'd be happy to delete everything on my server, set up a new sync with a new root folder, and report back what happens.
I have backups of my original bookmarks so it doesn't really matter if the extension messes them up as I can always disable the extension, delete everything, and restore my originals from backup.
@marcelklehr commented on GitHub (Mar 18, 2018):
Syncing your nextcloud account to a newly created folder (go to floccus options -> 'options' in your account -> Sync folder # reset) should work, then you can remove everything in there to remove everything on the server. Afterward you will need to restore your bookmarks in your browser to the way they were.
@marcelklehr commented on GitHub (Mar 18, 2018):
Oh, and I need the bookmarks app version you have installed on your nextcloud.
@marcelklehr commented on GitHub (Mar 24, 2018):
Any news on this?
EDIT: You may want to try the latest unreleased changes to the bookmarks app, which add a bulk editing feature.
@mobamoba commented on GitHub (Mar 24, 2018):
Sorry I spaced this. I'll set it up then see how it goes over the next few days with floccus only syncing to the floccus subfolder.
Thinking about it though, I wonder if the reason I wound up with all those dupes had something to do with using Floccus on Chrome as well as Firefox, like maybe Floccus thought they were different bookmarks when really they were the same set of bookmarks.
ETA: Just tried it again and it never finishes syncing (and keeps eating CPU). Floccus hangs at bookmark 621 out of about 700.
@marcelklehr commented on GitHub (Mar 24, 2018):
It stops during the initial sync with a new folder? Can you provide a (censored) log?
Firefox
about:debuggingdebugbutton next to floccus entrySync nowfor the account of your choice.@mobamoba commented on GitHub (Mar 25, 2018):
I let the sync run for over an hour and it never finished. Plus it was sucking up so much CPU that my browser dragged to a crawl. Here are the errors from the debug log:
@marcelklehr commented on GitHub (Mar 25, 2018):
@mobamoba If that is your real host, username and password in the logs, please change them now in nextcloud, for your own protection...
@mobamoba commented on GitHub (Mar 25, 2018):
Ugh thanks. Changed all the login info to be safe.
@marcelklehr commented on GitHub (Mar 25, 2018):
So, I couldn't gather much from the logs, sadly. It may be best to remove the 2000 bookmarks from nextcloud. You should be able to do that with the new bookmarks app UI, which has not yet been released. I've attached a build of the latest changes to make it easier for you to install: Simply extract the archive over the bookmarks app directory on your nextcloud server.
bookmarks-build-latest.tar.gz
@mobamoba commented on GitHub (Mar 25, 2018):
Okay but I'm not sure what else I can provide you other than the logs. What else would help debug this?
@marcelklehr commented on GitHub (Mar 25, 2018):
You could check the network tab in the debug console during syncing. It should show the network traffic between floccus and nextcloud.
@mobamoba commented on GitHub (Mar 25, 2018):
The new version of Bookmarks didn't work unfortunately.
@marcelklehr commented on GitHub (Mar 25, 2018):
oh. What happened? You may need to disable the app, and re-enable it.
@mobamoba commented on GitHub (Mar 25, 2018):
Yeah I did that. The Bookmarks page just had a swirling circle on it but nothing ever loaded.
@marcelklehr commented on GitHub (Mar 25, 2018):
Mmmh. Ctrl+F5 / F5 ?
@mobamoba commented on GitHub (Mar 25, 2018):
I did everything - even deleted the /apps/bookmarks directory and added it back. Still didn't work. Ended up deleting the new version and reverting to the old which doesn't let me bulk delete.
@marcelklehr commented on GitHub (Mar 25, 2018):
sigh ok, I'm sorry that didn't work.
EDIT: You could also remove all bookmarks using SQL :D
@marcelklehr commented on GitHub (Mar 26, 2018):
(In order to remove bookmarks on nextcloud using SQL you can use
TRUNCATE TABLE oc_bookmarks;andTRUNCATE TABLE oc_bookmarks_tags;)I've released a new version of floccus which has some fixes which might solve this issue, but hopefully also errors before creating any duplicates on its own in the future, so we I can investigate why that happens at all.
@mobamoba commented on GitHub (Mar 27, 2018):
I deleted the bookmarks. However, with the new version, absolutely nothing happens, no sync, nothing. It connects, syncs for 1 second, uploads nothing, then declares a successful sync. The only new thing in the debug log is:
Received bookmarks from server Array [ ]@marcelklehr commented on GitHub (Mar 27, 2018):
Does resetting the sync folder help? Make sure to not set it to the old folder. Otherwise it'll upload all your duplicates again... 🙈
The empty array is good as it indicates floccus has received all bookmarks from the server (there are none on there, right?).
@mobamoba commented on GitHub (Mar 27, 2018):
Resetting didn't make a difference. And, right, it's not downloading anything but it's also not uploading anything.
@marcelklehr commented on GitHub (Mar 27, 2018):
Ok, so there's still something fundamentally wrong, somehow. Mmh. You could run the newly built-in tests, which are not exhaustive, yet, but might give an indication as to where the problem lies. The link is in the bottom right corner of the options panel.
@mobamoba commented on GitHub (Mar 27, 2018):
How do you copy/paste the test error messages? I can't seem to select them - it's the same error over and over a timeout 2000ms promise resolve error. Also, running the tests killed the addon, i.e. Floccus now does absolutely nothing.
@marcelklehr commented on GitHub (Mar 27, 2018):
Awesome! We've poked the bear at the right spot. It's responding! 🐻
The timeout means that some method takes too long to respond. Which tests are failing specifically? All of them?
In order to make floccus work again you will have to re-install it, I'm afraid. This is not a feature of the tests, btw, but a shortcoming I inadvertently introduced... After all, the tests were not intended to be used just yet.
EDIT: If re-installing doesn't fix it. Open the addon debugger again, go to the scratchpad tab (if you can't see it, enable it in the options at the top right), paste the following and click 'Run':
@mobamoba commented on GitHub (Mar 28, 2018):
Here's a screenshot:
@marcelklehr commented on GitHub (Mar 28, 2018):
Thank you so much for bearing with me! I have it nailed down to one function that apparently recurses infinitely due to certain circumstances. How long have you had the firefox profile you tried this in? I'm guessing it's from a long-living firefox installation that has been updated continuously and during one of those upgrades mozilla missed to adjust one particular thing in their migrations of the bookmark data (no fault on your part). It's only a theory at this point, but could you try creating a new profile and running the tests there, too?
@mobamoba commented on GitHub (Mar 28, 2018):
Actually this is a pretty new computer so my Firefox profile is maybe 2 or 3 weeks old so that shouldn't be the problem.
@marcelklehr commented on GitHub (Mar 29, 2018):
Mmh. Maybe they did the change recently, then, but I can't replicate this in my installation of firefox v59.0.2. Or something else altered the bookmarks folders. Could you still try the tests with a fresh profile?
@phreaker0 commented on GitHub (Mar 29, 2018):
I don't know if this related but I get local duplicates if I reset the sync folder, set it to the old one and let it sync. It passes and creates some duplicates, the next sync will complain that there are local duplicates.
@mobamoba commented on GitHub (Mar 29, 2018):
So the syncing nothing was user error as I forgot to set the proper bookmark sync folder.
That aside, Floccus is still doing the same thing. It never really finishes the sync process, uses an enormous amount of CPU, and keeps creating local duplicates.
After getting over the user error above, I ran a sync to my completely empty Nextcloud Bookmarks instance meaning there were no chance of duplicates because there was nothing in Nextcloud to duplicate. Floccus synced then created a bunch of dupes and complained about them in the debug log. Weirdly, it also created an entirely new name for one of the dupes it created.
I deleted the dupes Floccus created and then got the following error:
SERVERDELETE snzfcKPuDhCk 15 Account.js:145:10 Response { type: "basic", url: "https://***", redirected: false, status: 200, ok: true, statusText: "OK", headers: Headers, bodyUsed: false } Nextcloud.js:309:4 SERVERDELETE EpythDIkXxBU 14 Account.js:145:10 SERVERDELETE JlvpQiWX5Tqk 8 Account.js:145:10 Response { type: "basic", url: "https://***", redirected: false, status: 400, ok: false, statusText: "Bad request", headers: Headers, bodyUsed: false } Nextcloud.js:309:4 Syncing failed with Error: Removing a bookmark on the server failed. remoteId=8 Stack trace: _callee5$@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/background-script.js:7419:23 tryCatch@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:6900:37 invoke@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:7138:22 defineIteratorMethods/</prototype[method]@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:6952:16 step@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/background-script.js:6731:183 step/<@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/background-script.js:6731:361 run@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:4295:22 notify/<@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:4308:30 flush@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:1398:9 Account.js:132:6 Response { type: "basic", url: "https://***…", redirected: false, status: 400, ok: false, statusText: "Bad request", headers: Headers, bodyUsed: false }@marcelklehr commented on GitHub (Mar 30, 2018):
Do you have the latest release of floccus already? (v2.0.1) The new version should error before creating duplicates, which I since believe to have resolved. The error with deleting the bookmarks from the server that are no longer there follows from the first one (but it's a distinct server issue that will be addressed in the next release of nextcloud bookmarks...)
@jayarc commented on GitHub (Mar 30, 2018):
There remains an issue for me on FF 60.0 with duplicates. I can't get things to sync my bookmarks toolbar. I typically have a few bookmarks in that bar that have no title and that is causing an issue. If you create a new bookmark in the toolbar and right click it, then select properties. In the properties dialog delete all the text in the Name: input and leave it blank, save. I do this to conserve space in the bar for websites that have favicons that show me enough to know what I'm clicking on. Floccus seems to have a problem with blank Names. There are related problems still even after I added names to all my toolbar stuff and tried again with truncated tables and fresh everything. Even with Names filled out I still get duplication errors on 2.0.2.
@jayarc commented on GitHub (Mar 30, 2018):
It duplicates items in the first level and child levels. Not all of the bookmarks get duplicated.
@jayarc commented on GitHub (Mar 30, 2018):
The duplicates that occured for me that were not on the first level of the folder all seem to have the pipe symbol in the Names ( | ). I'm not sure if there could be some character set related issue going on...
@marcelklehr commented on GitHub (Mar 30, 2018):
@jayarc I can't reproduce this with either pipes in the title nor empty titles with Fx v59, I doubt the firefox version is the problem, but I can't rule it out. Could you try running the tests and post the results? This is the most effective way to find out what exactly goes wrong.
@jayarc commented on GitHub (Mar 30, 2018):
I get no failures from the tests but I do get this output from debugging when I try to sync:
Starting sync process for account jason@https://example.com Account.js:105:6
SERVERDELETE XOGLx9sZJEWu 2 Account.js:140:10
SERVERDELETE zhvKW32W2LGu 3 Account.js:140:10
SERVERDELETE hsdH6ayajzYM 4 Account.js:140:10
Response { type: "basic", url: "https://example.com/inde…", redirected: false, status: 400, ok: false, statusText: "Bad request", headers: Headers, bodyUsed: false } Nextcloud.js:313:4
Response { type: "basic", url: "https://example.com/inde…", redirected: false, status: 400, ok: false, statusText: "Bad request", headers: Headers, bodyUsed: false } Nextcloud.js:313:4
Response { type: "basic", url: "https://example.com/inde…", redirected: false, status: 400, ok: false, statusText: "Bad request", headers: Headers, bodyUsed: false } Nextcloud.js:313:4
Syncing failed with Error: 3 errors
Stack trace:
MultiError@moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/background-script.js:14:9
next/<@moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/background-script.js:133:36
run@moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/polyfill.js:4295:22
notify/<@moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/polyfill.js:4308:30
flush@moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/polyfill.js:1398:9
Account.js:128:6
_callee8$ Account.js:128:6
tryCatch moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/polyfill.js:6900:37
invoke moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/polyfill.js:7138:22
defineIteratorMethods/</prototype[method] moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/polyfill.js:6952:16
step moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/background-script.js:4288:183
step/< moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/background-script.js:4288:402
run moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/polyfill.js:4295:22
notify/< moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/polyfill.js:4308:30
flush moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/polyfill.js:1398:9
Starting sync process for account jason@https://example.com Account.js:105:6
SERVERDELETE XOGLx9sZJEWu 2 Account.js:140:10
SERVERDELETE zhvKW32W2LGu 3 Account.js:140:10
SERVERDELETE hsdH6ayajzYM 4 Account.js:140:10
Response { type: "basic", url: "https://example.com/inde…", redirected: false, status: 400, ok: false, statusText: "Bad request", headers: Headers, bodyUsed: false } Nextcloud.js:313:4
Response { type: "basic", url: "https://example.com/inde…", redirected: false, status: 400, ok: false, statusText: "Bad request", headers: Headers, bodyUsed: false } Nextcloud.js:313:4
Response { type: "basic", url: "https://example.com/inde…", redirected: false, status: 400, ok: false, statusText: "Bad request", headers: Headers, bodyUsed: false } Nextcloud.js:313:4
Syncing failed with Error: 3 errors
Stack trace:
MultiError@moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/background-script.js:14:9
next/<@moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/background-script.js:133:36
run@moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/polyfill.js:4295:22
notify/<@moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/polyfill.js:4308:30
flush@moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/polyfill.js:1398:9
Account.js:128:6
_callee8$ Account.js:128:6
tryCatch moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/polyfill.js:6900:37
invoke moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/polyfill.js:7138:22
defineIteratorMethods/</prototype[method] moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/polyfill.js:6952:16
step moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/background-script.js:4288:183
step/< moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/background-script.js:4288:402
run moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/polyfill.js:4295:22
notify/< moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/polyfill.js:4308:30
flush moz-extension://a4af6b1c-8124-4b38-8420-9bd33cc55c15/dist/js/polyfill.js:1398:9
@marcelklehr commented on GitHub (Mar 30, 2018):
@jayarc Nextcloud bookmark refuses to delete bookmarks that don't exist. This is a bug in nextcloud bookmarks, but it may be triggered by a bug in floccus, since it shouldn't remove bookmarks that are not existent on the server. No tests are failing, yet you get duplicates from syncing. :/
@jayarc commented on GitHub (Mar 30, 2018):
So in theory, things should operate normally and pretty stable even despite these errors, which is what I thought I was seeing. Thank you all for your work on floccus it's a god send for my self-hosted ways and I appreciate it!
@marcelklehr commented on GitHub (Mar 30, 2018):
Thanks for the kind words :) So, you don't get any errors about duplicates anymore?
@jayarc commented on GitHub (Mar 30, 2018):
I ended up deleting the dupes and the originals and I'll just recreate those for now and see. I'm not quite sure either about the pipe character being a problem or the blank name to be honest I feel like I worked around it for now.
@marcelklehr commented on GitHub (Apr 2, 2018):
Appearance of random duplicates should be fixed in the latest release. Please try it out and give feedback :)
@mobamoba commented on GitHub (Apr 3, 2018):
Does it scan the current bookmarks on the server first or do I need to wipe those and start over again?
@jayarc commented on GitHub (Apr 3, 2018):
Things have worked themselves out on my end it seems fixed, testing on a second machine proved to work perfectly. Thanks for all the hard work :)
@marcelklehr commented on GitHub (Apr 3, 2018):
@mobamoba It should work without wiping the server. :)
@jayarc Awesome. I'm glad it works for you now :)
@jayarc commented on GitHub (Apr 3, 2018):
I can confirm it worked without wiping anything. The three errors just went away and things work normally for me. I then synced that folder to another machine with no problems.
@jayarc commented on GitHub (Apr 3, 2018):
The only thing I notice that's different on machine 2 is that the ordering of the bookmarks (I'm using only the bookmarks toolbar folder synced) is different on the second machine than it was set on the first.
@jayarc commented on GitHub (Apr 3, 2018):
I'll try ordering them on machine 2 and see if 1 is adjusted accordingly.
@marcelklehr commented on GitHub (Apr 3, 2018):
The order is not possible to be synced, atm.
@jayarc commented on GitHub (Apr 3, 2018):
Ah I see I set it per machine/profile thanks!
@mobamoba commented on GitHub (Apr 3, 2018):
Even after removing Floccus, restarting Firefox, and reinstalling, there's no way to add an account. Nothing comes up in the Options setting and clicking the icon brings up an empty box.
@marcelklehr commented on GitHub (Apr 3, 2018):
@mobamoba That particular bug should be fixed in the latest version, actually :/ Are you sure you got the latest one? Which version did you install?
@mobamoba commented on GitHub (Apr 3, 2018):
2.0.5 - the one up on the official Firefox site.
@marcelklehr commented on GitHub (Apr 3, 2018):
Does https://github.com/marcelklehr/floccus/issues/54#issuecomment-376588594 work?
@mobamoba commented on GitHub (Apr 3, 2018):
Nothing works. The options page opens nothing other than the description portion.
@marcelklehr commented on GitHub (Apr 3, 2018):
Then we will need to open the debugger again and have a peek at the console. (
about:debugging)@mobamoba commented on GitHub (Apr 3, 2018):
``Error: Could not establish connection. Receiving end does not exist. undefined
Unknown property ‘-moz-osx-font-smoothing’. Declaration dropped. bootstrap.css:32:27
Unknown property ‘zoom’. Declaration dropped. base.css:4:20
Expected media feature name but found ‘-Webkit-min-device-pixel-ratio’. base.css:187:25
Expected media feature name but found ‘-moz-min-device-pixel-ratio’. base.css:187:79
Expected media feature name but found ‘-o-min-device-pixel-ratio’. base.css:187:129
Expected media feature name but found ‘min-device-pixel-ratio’. base.css:187:177
Error in parsing value for ‘background-image’. Declaration dropped. base.css:189:69
Expected media feature name but found ‘-Webkit-min-device-pixel-ratio’. base.css:288:25
Expected media feature name but found ‘-moz-min-device-pixel-ratio’. base.css:288:79
Expected media feature name but found ‘-o-min-device-pixel-ratio’. base.css:288:129
Expected media feature name but found ‘min-device-pixel-ratio’. base.css:288:177
Expected media feature name but found ‘-Webkit-min-device-pixel-ratio’. popup.css:96:25
Expected media feature name but found ‘-moz-min-device-pixel-ratio’. popup.css:96:79
Expected media feature name but found ‘-o-min-device-pixel-ratio’. popup.css:96:129
Expected media feature name but found ‘min-device-pixel-ratio’. popup.css:96:177
Expected media feature name but found ‘-Webkit-min-device-pixel-ratio’. popup.css:310:25
Expected media feature name but found ‘-moz-min-device-pixel-ratio’. popup.css:310:79
Expected media feature name but found ‘-o-min-device-pixel-ratio’. popup.css:310:129
Expected media feature name but found ‘min-device-pixel-ratio’. popup.css:310:177
Expected media feature name but found ‘-Webkit-min-device-pixel-ratio’. popup.css:466:25
Expected media feature name but found ‘-moz-min-device-pixel-ratio’. popup.css:466:79
Expected media feature name but found ‘-o-min-device-pixel-ratio’. popup.css:466:129
Expected media feature name but found ‘min-device-pixel-ratio’. popup.css:466:177
Expected media feature name but found ‘-Webkit-min-device-pixel-ratio’. popup.css:493:25
Expected media feature name but found ‘-moz-min-device-pixel-ratio’. popup.css:493:79
Expected media feature name but found ‘-o-min-device-pixel-ratio’. popup.css:493:129
Expected media feature name but found ‘min-device-pixel-ratio’. popup.css:493:177
Error in parsing value for ‘padding-top’. Declaration dropped. popup.css:1517:14
Unknown property ‘-moz-border-radius’. Declaration dropped. popup.css:1666:21
Unknown property ‘-moz-box-shadow’. Declaration dropped. popup.css:1685:19
Unknown pseudo-class or pseudo-element ‘-webkit-scrollbar’. Ruleset ignored due to bad selector. popup.css:1706:2
Unknown pseudo-class or pseudo-element ‘-webkit-scrollbar-track-piece’. Ruleset ignored due to bad selector. popup.css:1709:2
Unknown pseudo-class or pseudo-element ‘-webkit-scrollbar-thumb’. Ruleset ignored due to bad selector. popup.css:1713:2
Unknown pseudo-class or pseudo-element ‘-webkit-search-cancel-button’. Ruleset ignored due to bad selector. popup.css:1975:20
Unknown pseudo-class or pseudo-element ‘-webkit-search-cancel-button’. Ruleset ignored due to bad selector. popup.css:1984:20
Error in parsing value for ‘font’. Declaration dropped. popup.css:2061:20
Error in parsing value for ‘-webkit-transition’. Declaration dropped. tooltip.css:15:64
Error in parsing value for ‘-moz-transition’. Declaration dropped. tooltip.css:16:60
Error in parsing value for ‘transition’. Declaration dropped. tooltip.css:18:56
Error in parsing value for ‘-webkit-transition’. Declaration dropped. tooltip.css:27:34
@marcelklehr commented on GitHub (Apr 3, 2018):
Mmh. All messages appear to be unrelated. Did you open the debugger first and then open / reload the options page? This ensures that errors thrown during page setup are caught in the debugger, but I doubt anything new will come up.
@mobamoba commented on GitHub (Apr 3, 2018):
I did that; that's all that came up.
@marcelklehr commented on GitHub (Apr 3, 2018):
Bummer. I'm sure this must be frustrating. Can you think of anything that might be different in your setup from other setups? e.g. locale, operating system, any specific settings like private browsing by default, etc.
@mobamoba commented on GitHub (Apr 4, 2018):
Well I've progressed a little. I can now create an account and select a folder but nothing happens. Sync Now is gray and pressing it does nothing even though it says it's syncing. Run Tests came out with all green checkmarks. Here's the debug log:
The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol. background.html
initializing account 7767867297 Account.js:73:4
Apparently not initialized, because: Error: Incorrect argument types for bookmarks.getSubTree.
Stack trace:
_callee7$@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/background-script.js:5181:24
tryCatch@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:6900:37
invoke@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:7138:22
defineIteratorMethods/</prototype[method]@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:6952:16
step@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/background-script.js:4900:183
_asyncToGenerator/</<@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/background-script.js:4900:437
Promise@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:4400:7
_asyncToGenerator/<@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/background-script.js:4900:99
isInitialized@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/background-script.js:5202:16
_callee5$@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/background-script.js:5056:24
tryCatch@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:6900:37
invoke@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:7138:22
defineIteratorMethods/</prototype[method]@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:6952:16
step@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/background-script.js:4900:183
_asyncToGenerator/</<@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/background-script.js:4900:437
Promise@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:4400:7
_asyncToGenerator/<@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/background-script.js:4900:99
tracksBookmark@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/background-script.js:5085:16
_callee2$@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/background-script.js:4681:63
tryCatch@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:6900:37
invoke@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:7138:22
defineIteratorMethods/</prototype[method]@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:6952:16
step@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/background-script.js:4521:183
_asyncToGenerator/</<@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/background-script.js:4521:437
Promise@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:4400:7
_asyncToGenerator/<@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/background-script.js:4521:99
_callee3$/</<@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/background-script.js:4692:28
_callee3$@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/background-script.js:4675:36
tryCatch@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:6900:37
invoke@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:7138:22
defineIteratorMethods/</prototype[method]@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:6952:16
step@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/background-script.js:4521:183
step/<@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/background-script.js:4521:361
run@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:4295:22
notify/<@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:4308:30
flush@moz-extension://2228ed28-f0ea-4359-a50b-3bb64047fe0b/dist/js/polyfill.js:1398:9
Account.js:98:6
TypeError: Argument 1 of StructuredCloneHolder.deserialize is not an object.[Learn More] ExtensionChild.jsm:897:24
Error: Could not establish connection. Receiving end does not exist. undefined
TypeError: Argument 1 of StructuredCloneHolder.deserialize is not an object.[Learn More] ExtensionChild.jsm:897:24
Error: Could not establish connection. Receiving end does not exist.
@marcelklehr commented on GitHub (Apr 4, 2018):
does the problem persist, if you delete the account, recreate it and then sync again?
@mobamoba commented on GitHub (Apr 4, 2018):
Well somehow the problem vanished and it now works on both Firefox and Chrome. I think Firefox was getting stuck in an account syncing loop of some kind because I noticed once I disabled account sync and restarted, I was able to work normally with Floccus. I re-enabled sync afterwards - perhaps all the bookmark changes "confused" Firefox in some with its on internal syncing mechanism or something. At any rate, it's all working thanks!
@marcelklehr commented on GitHub (Apr 4, 2018):
Phew. I'm glad it works, now. 😅
Re internal syncing mechanism: Do you have Firefox sync enabled?
@mobamoba commented on GitHub (Apr 5, 2018):
Yes I do.
@marcelklehr commented on GitHub (Apr 5, 2018):
Ah, please don't. Firefox Sync is known to cause problems, because it changes the IDs of your bookmarks and floccus is left out in the cold.
@mobamoba commented on GitHub (Apr 5, 2018):
Oh okay. I didn't see a notation of that anywhere so I didn't know. I'll leave Firefox Sync off for Bookmarks but on for everything else - that should be fine right?
@marcelklehr commented on GitHub (Apr 5, 2018):
I think so, yep. I see, I'll try to make it more prominent in the README as well :)
@mobamoba commented on GitHub (Apr 5, 2018):
Yeah, I only looked at the Firefox Install section on the main page then at the description on the AMO site - I'd stick in all-caps in both places because Firefox Sync was, I think, definitely the source of some of the problems.
@github-actions[bot] commented on GitHub (Mar 21, 2023):
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.