Tabliss resets to default settings on major browsers (including Chrome-based browsers & Firefox) #268

Hanif1601 · 2020-07-11T08:15:55Z

When I opened my browsers like Google Chrome, new Microsoft Edge, and even Brave, Tabliss discards your personalized widgets and reset to default one. This happened almost every time when I launch the browser and rather annoying. This only affected to Chrome-based browsers only (except Vivaldi, interestingly). I don't know why the extension suddenly resets to default for no reason. Is the Tabliss having a problem or maybe some experimental flags that I enabled on my browsers?

jcgaza · 2020-07-29T09:11:17Z

+1 on Firefox and Firefox Developer Edition. It's very frustrating when this happens. Hope this gets fixed.

Reboot-Codes · 2020-07-31T19:48:32Z

Yes, this happens in vanilla chrome (no flags, no other extensions). Only when restarting chrome, not when opening a new window.

julianatfg · 2020-08-04T16:47:59Z

Yes, same here. I just submitted a support ticket through the extension. I hope this gets fixed soon.

+1 on Firefox and Firefox Developer Edition. It's very frustrating when this happens. Hope this gets fixed.

6RASi · 2020-08-05T12:50:54Z

+1 on Firefox and Firefox Developer Edition. It's very frustrating when this happens. Hope this gets fixed.

Also have this issue with Firefox. Amazing extension but I don't feel like doing my settings daily. Hopefully a fix is coming or at least some acknowledgement of the issue since it's a big issue.

Hanif1601 · 2020-08-05T12:56:05Z

+1 on Firefox and Firefox Developer Edition. It's very frustrating when this happens. Hope this gets fixed.

Also have this issue with Firefox. Amazing extension but I don't feel like doing my settings daily. Hopefully a fix is coming or at least some acknowledgement of the issue since it's a big issue.

Ah, Firefox issued this too. Alrighty.

trickypr · 2020-08-06T22:05:45Z

I can't reproduce this issue (yet). Could someone provide more information so I can try and figure out what is going on:

What OS are you running?
If you open the web console (right click, press inspect element, click the console tab) are there any errors in there?
Do you have any software installed on your computer that could be messing with addon storage, for example CCleaner?

julianatfg · 2020-08-06T22:21:35Z

I can't reproduce this issue (yet). Could someone provide more information so I can try and figure out what is going on:

* What OS are you running?

* If you open the web console (right click, press inspect element, click the console tab) are there any errors in there?

* Do you have any software installed on your computer that could be messing with addon storage, for example [CCleaner](https://mspoweruser.com/ccleaner-is-now-deleting-synched-firefox-extension-data/)?

Windows 10, version 20H2, compilation 19042.423;
I only get this as an error:

Error in parsing value for ‘-webkit-text-size-adjust’. Declaration dropped. main.css:13:29 Elements matching selector: html NodeList(1) 0: <html lang="en"> length: 1 <prototype>: NodeListPrototype constructor: function () entries: function entries() forEach: function forEach() item: function item() keys: function keys() length: values: function values() Symbol(Symbol.iterator): function values() Symbol(Symbol.toStringTag): "NodeList" <get length()>: function length() <prototype>: {…

Nope. I checked the uBlock origin add-on but it remains disabled on Tabliss, so, I don't think there's any need to disable that?

trickypr · 2020-08-06T22:36:22Z

Ublock should be fine

PyvesB · 2020-08-08T16:54:17Z

I've just lost all my Tabliss defaults today for the first time since I started using it on Firefox a few years ago. This happened just after a Windows update (KB4562900), not sure whether it's a coincidence or a possible cause.

julianatfg · 2020-08-09T16:54:50Z

I've just lost all my Tabliss defaults today for the first time since I started using it on Firefox a few years ago. This happened just after a Windows update (KB4562900), not sure whether it's a coincidence or a possible cause.

As far as I could check in the Windows Update site, I haven't got that update installed as I'm on the Insider programme and therefore I'm a few compilations ahead. Although the issues treated on that cumulative update were also probably addressed in the compilation I have installed, I would think? So I'd be susceptible to the same issues/bugs as you.

Anyway. I've just opened Firefox for the first time today and no sign of resetting to the default configs. Mine are intact, so far 🥳

ghost · 2020-08-10T18:18:27Z

+1 on Firefox

Tabliss used to work perfectly, but with the last update (Firefox 79.0, July 28 2020) Tabliss resets its configuration with every run.
I'm on Ubuntu 20.04.

trickypr · 2020-08-10T22:09:28Z

Mozilla made some changes to the Firefox storage.sync Api with Firefox 79. I suspect that the addon can’t handle these changes properly. More information about the migration is available at: https://blog.mozilla.org/addons/2020/07/09/changes-to-storage-sync-in-firefox-79/

julianatfg · 2020-08-11T21:33:54Z

I'm on Firefox Developer Edition 80.0b6 (64-bit) and, for a few days, my Tabliss configs haven't reset to default, thankfully!

Hanif1601 · 2020-08-12T01:41:36Z

@trickypr

OS: Windows 10 Pro, version 1709 (Fall Creators)
I didn't get any errors at all on Google Chrome & Microsoft Edge
I do have CCleaner but I never used it and also using outdated version

jcgaza · 2020-08-12T11:08:28Z

I'm on Firefox Developer Edition 80.0b6 (64-bit) and, for a few days, my Tabliss configs haven't reset to default, thankfully!

Unfortunately, not for me. A few moments ago, it reset to default after I installed an update for Firefox Developer Edition. I'm running on an Xubuntu 16.04. There were no logs on the console as well.

BalinGrant · 2020-08-22T05:09:34Z

Happening for me on Chrome Canary with following extensions https://gyazo.com/4c2410a7c1d79368275d704d03b2d68e

trickypr · 2020-08-22T08:32:22Z

I am struggling to figure out what this is. I suspect that this has something to do with #277, but I am not skilled enough at debugging to figure out the source of the error. If anyone can, I am happy to take another look into it.

julianatfg · 2020-08-22T19:46:17Z

I know this is not much help but since my last comment, I haven't experienced any resets. So, I don't know what was up. I constantly use both Firefox 79.0 and Firefox Developer 80.0b8 (both 64-bit) and neither have reset my configs as of yet.

julianatfg · 2020-08-29T16:45:01Z

WELL. Now it started resetting on its own again this week. So much for thinking the problem has been cleared away all by itself. Crap 😫

(I'm now on FF Dev Edition 81.0b3, and FF [stable channel] 80.0.)

The console now displays the following error message:

13:46:03.586 Error in parsing value for ‘-webkit-text-size-adjust’. Declaration dropped. main.css:13:29 Elements matching selector: html NodeList(1) 0: <html lang="en"> length: 1 <prototype>: NodeListPrototype constructor: () length: 0 name: "NodeList" prototype: NodeListPrototype { item: item(), keys: keys(), values: values(), … } Symbol(Symbol.hasInstance): function Symbol.hasInstance() <prototype>: function () entries: entries() length: 0 name: "entries" <prototype>: function () forEach: forEach() length: 1 name: "forEach" <prototype>: function () item: item() length: 1 name: "item" <prototype>: function () keys: keys() length: 0 name: "keys" <prototype>: function () length: values: values() length: 0 name: "values" <prototype>: function () Symbol(Symbol.iterator): values() length: 0 name: "values" <prototype>: function () Symbol(Symbol.toStringTag): "NodeList" <get length()>: length() length: 0 name: "get length" <prototype>: function () <prototype>: {…} __defineGetter__: function __defineGetter__() __defineSetter__: function __defineSetter__() __lookupGetter__: function __lookupGetter__() __lookupSetter__: function __lookupSetter__() __proto__: constructor: function Object() hasOwnProperty: function hasOwnProperty() isPrototypeOf: function isPrototypeOf() propertyIsEnumerable: function propertyIsEnumerable() toLocaleString: function toLocaleString() toString: function toString() valueOf: function valueOf() <get __proto__()>: function __proto__() <set __proto__()>: __proto__()

Hanif1601 · 2020-08-30T05:04:27Z

WELL. Now it started resetting on its own again this week. So much for thinking the problem has been cleared away all by itself. Crap 😫

(I'm now on FF Dev Edition 81.0b3, and FF [stable channel] 80.0.)

The console now displays the following error message:

13:46:03.586 Error in parsing value for ‘-webkit-text-size-adjust’. Declaration dropped. main.css:13:29 Elements matching selector: html NodeList(1) 0: <html lang="en"> length: 1 <prototype>: NodeListPrototype constructor: () length: 0 name: "NodeList" prototype: NodeListPrototype { item: item(), keys: keys(), values: values(), … } Symbol(Symbol.hasInstance): function Symbol.hasInstance() <prototype>: function () entries: entries() length: 0 name: "entries" <prototype>: function () forEach: forEach() length: 1 name: "forEach" <prototype>: function () item: item() length: 1 name: "item" <prototype>: function () keys: keys() length: 0 name: "keys" <prototype>: function () length: values: values() length: 0 name: "values" <prototype>: function () Symbol(Symbol.iterator): values() length: 0 name: "values" <prototype>: function () Symbol(Symbol.toStringTag): "NodeList" <get length()>: length() length: 0 name: "get length" <prototype>: function () <prototype>: {…} __defineGetter__: function __defineGetter__() __defineSetter__: function __defineSetter__() __lookupGetter__: function __lookupGetter__() __lookupSetter__: function __lookupSetter__() __proto__: constructor: function Object() hasOwnProperty: function hasOwnProperty() isPrototypeOf: function isPrototypeOf() propertyIsEnumerable: function propertyIsEnumerable() toLocaleString: function toLocaleString() toString: function toString() valueOf: function valueOf() <get __proto__()>: function __proto__() <set __proto__()>: __proto__()

Whoa, that's a lot of errors!

trickypr · 2020-08-30T06:58:36Z

WELL. Now it started resetting on its own again this week. So much for thinking the problem has been cleared away all by itself. Crap 😫
(I'm now on FF Dev Edition 81.0b3, and FF [stable channel] 80.0.)
The console now displays the following error message:

13:46:03.586 Error in parsing value for ‘-webkit-text-size-adjust’. Declaration dropped. main.css:13:29 Elements matching selector: html NodeList(1)  0: <html lang="en">  length: 1  <prototype>: NodeListPrototype  constructor: ()  length: 0  name: "NodeList"  prototype: NodeListPrototype { item: item(), keys: keys(), values: values(), … }  Symbol(Symbol.hasInstance): function Symbol.hasInstance()  <prototype>: function ()  entries: entries()  length: 0  name: "entries"  <prototype>: function ()  forEach: forEach()  length: 1  name: "forEach"  <prototype>: function ()  item: item()  length: 1  name: "item"  <prototype>: function ()  keys: keys()  length: 0  name: "keys"  <prototype>: function ()  length:  values: values()  length: 0  name: "values"  <prototype>: function ()  Symbol(Symbol.iterator): values()  length: 0  name: "values"  <prototype>: function ()  Symbol(Symbol.toStringTag): "NodeList"  <get length()>: length()  length: 0  name: "get length"  <prototype>: function ()  <prototype>: {…}  __defineGetter__: function __defineGetter__()  __defineSetter__: function __defineSetter__()  __lookupGetter__: function __lookupGetter__()  __lookupSetter__: function __lookupSetter__()  __proto__:  constructor: function Object()  hasOwnProperty: function hasOwnProperty()  isPrototypeOf: function isPrototypeOf()  propertyIsEnumerable: function propertyIsEnumerable()  toLocaleString: function toLocaleString()  toString: function toString()  valueOf: function valueOf()  <get __proto__()>: function __proto__()  <set __proto__()>: __proto__()

Whoa, that's a lot of errors!

Unfortunately that is just a css error. That is safari code that Firefox doesn't understand. Firefox just logs a warning and moves on. It isn't something related to the storage code.

julianatfg · 2020-08-30T15:44:51Z

WELL. Now it started resetting on its own again this week. So much for thinking the problem has been cleared away all by itself. Crap 😫
(I'm now on FF Dev Edition 81.0b3, and FF [stable channel] 80.0.)
The console now displays the following error message:

13:46:03.586 Error in parsing value for ‘-webkit-text-size-adjust’. Declaration dropped. main.css:13:29 Elements matching selector: html NodeList(1)  0: <html lang="en">  length: 1  <prototype>: NodeListPrototype  constructor: ()  length: 0  name: "NodeList"  prototype: NodeListPrototype { item: item(), keys: keys(), values: values(), … }  Symbol(Symbol.hasInstance): function Symbol.hasInstance()  <prototype>: function ()  entries: entries()  length: 0  name: "entries"  <prototype>: function ()  forEach: forEach()  length: 1  name: "forEach"  <prototype>: function ()  item: item()  length: 1  name: "item"  <prototype>: function ()  keys: keys()  length: 0  name: "keys"  <prototype>: function ()  length:  values: values()  length: 0  name: "values"  <prototype>: function ()  Symbol(Symbol.iterator): values()  length: 0  name: "values"  <prototype>: function ()  Symbol(Symbol.toStringTag): "NodeList"  <get length()>: length()  length: 0  name: "get length"  <prototype>: function ()  <prototype>: {…}  __defineGetter__: function __defineGetter__()  __defineSetter__: function __defineSetter__()  __lookupGetter__: function __lookupGetter__()  __lookupSetter__: function __lookupSetter__()  __proto__:  constructor: function Object()  hasOwnProperty: function hasOwnProperty()  isPrototypeOf: function isPrototypeOf()  propertyIsEnumerable: function propertyIsEnumerable()  toLocaleString: function toLocaleString()  toString: function toString()  valueOf: function valueOf()  <get __proto__()>: function __proto__()  <set __proto__()>: __proto__()

Whoa, that's a lot of errors!

Unfortunately that is just a css error. That is safari code that Firefox doesn't understand. Firefox just logs a warning and moves on. It isn't something related to the storage code.

Yeah, I knew as much but just thought to throw it out there as Console gave me that message (which was far longer than the previous error message).

trmdi · 2020-09-04T01:34:08Z

+1
On my machine (Firefox 79 on Linux), it's lost after several restart randomly.

Hanif1601 · 2020-09-21T02:42:55Z

+1
On my machine (Firefox 79 on Linux), it's lost after several restart randomly.

OOF.

afcady · 2020-10-11T22:47:22Z

Saw some interesting behavior just now in Firefox 76.0.1. After starting the browser, the first tab opened kept the settings. But in every other tab opened, the settings had been reset to default.

trmdi · 2020-10-17T12:24:41Z

Trying this addon again in FF 81.0.1 and the settings still has been being kept for several days...
Update 1: it's still kept after 11 days (FF 82.0)
Update 2: it gets lost again :(

PaMaBa1806 · 2020-11-03T15:40:25Z

Hey, I'm also experiencing the error... Whenever I close Firefox and later reopen it, the settings of Tabliss are reset... I really like this extension very much, but if this goes on for a long time, I will have to look for another extension.
Can the developer please take care of this problem again? Thanks!

My components:

OS: Windows 10 Home (2004)
Firefox: 82.0.2 (64-bit)

Cheers,
PaMaBa1806

trickypr · 2022-01-07T09:08:05Z

I am in the process of moving my firefox profile onto a ram disk, so I will test and see if I can reproduce on linux.

I'm very interested to hear your test results. Which RAM disk utility are you using?

I am using tmpfs (one of the ramdisks built into the linux kernel) controlled by Profile-sync-daemon which should handle persistence between reboots.

Update: Tabliss seems to be working, so I am going to try running firefox from an artificially slow partition.

Gitoffthelawn · 2022-01-07T10:03:37Z

I am using tmpfs (one of the ramdisks built into the linux kernel) controlled by Profile-sync-daemon which should handle persistence between reboots.

Update: Tabliss seems to be working, so I am going to try running firefox from an artificially slow partition.

Thanks for the info. :)

Which version of Firefox are you using for testing?

trickypr · 2022-01-07T10:05:28Z

95.0.2 via the manjaro stable repos

ToddIndry37 · 2022-01-07T13:42:37Z

Update: So, I tried make it as home page on my Firefox, it seems the settings and customization didn't reset on Developer Edition 96.0b10. Also on Edge, it didn't reset same as Firefox. So uh, problem solved from browser themselves?

joelshepherd · 2022-01-07T16:41:49Z

My (current) going theory is if Tabliss fails to load your settings for whatever reason (possibly from a browser bug or even a momentary disk failure), Tabliss assumes you have no settings and writes it's default configuration to the database, overwriting any setting you may of had saved otherwise.

I cannot be certain this is the issue, but the storage will become less brittle in general if I stopped writing the default settings to the database if they don't exist.

I will continue to monitor this thread though in case I find any other leads.

Side question though: For anyone having this resets, are you using "Firefox Sync" perchance?

Gitoffthelawn · 2022-01-07T22:09:00Z

My (current) going theory is if Tabliss fails to load your settings for whatever reason (possibly from a browser bug or even a momentary disk failure), Tabliss assumes you have no settings and writes it's default configuration to the database, overwriting any setting you may of had saved otherwise.

I cannot be certain this is the issue, but the storage will become less brittle in general if I stopped writing the default settings to the database if they don't exist.

I like that idea.

Another possible solution could be to wait 250ms and try again. Do that x times (where a reasonable value for x is probably 4-8), and if it still fails, then write default configuration.

Also, as a stopgap measure, you could prompt the user with a message that says something like "Welcome to Tabliss. Initializing settings. Press "OK" to continue or "Cancel" to use previous settings.".

I will continue to monitor this thread though in case I find any other leads.

Thanks.

Side question though: For anyone having this resets, are you using "Firefox Sync" perchance?

Not I. But note that even with Firefox Sync completely disabled and no Firefox account ever used in a profile, Firefox still writes data to its local sync databases. It's a longstanding privacy issue that Mozilla really needs to fix. To be totally fair, I haven't checked for a few months to see if the issue still exists, but the last 20+ times I checked, it did.

ToddIndry37 · 2022-01-09T03:58:58Z

Update 2: Now on Edge suddenly reset themselves after updating to 98.0.1108.15. No error on console logs at all. Firefox still fine. Not sure if this was browser problem.

Xoouu · 2022-01-09T11:01:29Z

Currently on this version of ungoogled-chromium: Version 96.0.4664.110 (Official Build, ungoogled-chromium) (64-bit)
There are no errors in the console but the settings resetted either way. Is it an extension conflicting with tabliss or something else?

ToddIndry37 · 2022-01-09T11:07:53Z

Is it an extension conflicting with tabliss or something else?

Probably it is. I might try to disable some extensions on Edge if there's something not right with Tabliss.

ToddIndry37 · 2022-01-09T11:19:01Z

Update 3: I think I found some suspect here that may possibly Tabliss discard or forget the settings & customization on Chromium-based browsers.

PS: This is on Microsoft Edge Dev 98.0.1108.15, so I think these also may same results on Chrome and others.

joelshepherd · 2022-02-08T11:14:06Z

Over the holidays I have rewritten the storage layer away from the current library and address the brittleness I spoke of earlier.

Once I've written the migration that allows you to import your existing settings I'll upload a build here for people with the issue to try it out. There is a lot less "magic" going on in the storage layer now, so I am hopeful!

If you are feeling particularly adventurous, you can try the build earlier by compiling the db branch from source. Buyers beware though, there are definitely bugs there 😂

ToddIndry37 · 2022-02-08T12:34:32Z

Over the holidays I have rewritten the storage layer away from the current library and address the brittleness I spoke of earlier.

Once I've written the migration that allows you to import your existing settings I'll upload a build here for people with the issue to try it out. There is a lot less "magic" going on in the storage layer now, so I am hopeful!

If you are feeling particularly adventurous, you can try the build earlier by compiling the db branch from source. Buyers beware though, there are definitely bugs there 😂

Ah, did you recently updated the database of the extension? What did you found so far during rewrite the entire database or something?

joelshepherd · 2022-02-08T14:47:18Z

Tabliss was original written with redux for state management, with the local storage was added on by rt2zz/redux-persist and a web extension driver. This didn't give me any control over the process of reading and writing local storage, so there wasn't much I could do about the brittleness I spoke of earlier.

Long story short, I have rewritten Tabliss's state layer away from redux to a more standard key-value database (similar to the actual local storage is the browser). In doing so I have a lot more control of reading from and writing to storage, and have been able to remove the brittle initialisation situation Tabliss currently has.

I still have a bit of work to do and tests to write, but I am pretty hopefully this will fix the issue for most people. Plus if people do have storage issues in the future, I now have more than a blackbox to work with!

joelshepherd · 2022-02-12T08:08:12Z

Hi all, the first beta build of Tabliss with the new storage layer is ready. Given I cannot reproduce this error myself, I would appreciate anyone who gets it on a (semi-)reliable basis to please test this new build. Let me know if Tabliss still resets on you, and if Tabliss alerts you to any storage errors when this occurs.

Hopefully Tabliss either works perfectly, or gives you a decent error message telling us what happened. If you do find Tabliss resets without telling you anything. Try not touching anything, restarting your browser, and see if your settings return.

For now, the beta build is only available on Firefox. To install:

Export your existing Tabliss settings
Uninstall your existing Tabliss extension
Download and extract the beta build: tabliss-2.2.0.3-firefox.zip
In Firefox's Add-ons Manager, click the cog, select "Install Add-on from File", and choose the extracted xpi file
Re-import your Tabliss settings from the earlier export

Remember it is a beta build, and you may come across other bugs unrelated to storage. I encourage anyone trying it to grab a backup of your settings before using it.

julianatfg · 2022-02-13T21:48:53Z

@joelshepherd I just installed the beta and we'll see how it goes! So far, so good (I've closed & reopened Firefox half a dozen times and no signs of the error.)

soumyaDghosh · 2022-02-18T03:53:41Z

I face this issue everytime when my firefox undergoes through an update I exported the settings so it's not that hassle now to restore settings.
My os is Ubuntu 21.10

trmdi · 2022-02-18T04:33:57Z

I face this issue everytime when my firefox undergoes through an update I exported the settings so it's not that hassle now to restore settings. My os is Ubuntu 21.10

Try the beta version right above your comment. It seems quite stable, I've found no issue until now...

joelshepherd · 2022-03-09T12:19:55Z

Hi everyone, I finally have a release candidate ready!

So if anyone has any feedback on whether the beta build solved the resetting for them, now it the time to let me know.

Install the release candidate for:
- Firefox: Install add-on from file tabliss-2.2.0.4-firefox.zip
- Chromium: Load unpacked extension from the latest build

If you used the previous beta build, your widget settings may not come across due to updates to the database layout (re-importing your old backup should recover them). If you haven't used the previous beta build, the release candidate will migrate all your settings automatically.

julianatfg · 2022-03-09T14:42:14Z

No issues so far. I first downloaded the FF beta 24 days ago (thnx github!) and I haven't had a reset since then. And most recently, I installed the Chromium version too and I haven't had issues with that either.

I'm just going to update both betas and will keep you posted on anything amiss. Thank you! 😸

Gitoffthelawn · 2022-03-11T07:38:25Z

So far it's working well. Thanks! If a problem arises, I'll be sure to post with detailed information.

mbierman · 2022-03-11T20:03:09Z

Interestingly, I'm fine on Chrome, but Safari (macOS) frequently resets to default and I have to reimport my settings.
Safari: Version 15.3 (17612.4.9.1.8)
macos: 12.2.1 (21D62)

joelshepherd · 2022-03-12T07:41:15Z

Hi @mbierman, how do you run Tabliss on Safari? Through the web version? If you email me your setup at [email protected] I can help troubleshoot the issue.

sonofevil · 2022-03-14T19:46:36Z

Layout reset once again. Version 2.3.0 on Waterfox G4.0.7
I also noticed that the background image settings didn't reset. Only the widgets.

From the timing I assume this must be related to the add-on auto-updating from 2.2.1 to 2.3.0.

mbierman · 2022-03-14T22:38:13Z

@joelshepherd yes, I use the web version.

Seems to be working for me so far. I think I had a custom CSS error. Since fixing that it seems good. If I have further issues I will include my config.

joelshepherd · 2022-03-19T06:47:26Z

It seems the resetting situation has improved for many people since the release of Tabliss 2.2; so I am going to (finally) resolve this issue, and save many people lots of extra spam 😂

For future reset bugs, I have created a new thread to report/investigate any post-2.2 resetting: #459

Thank you for everyone who reported, investigated, and provided beta feedback over the life of this issue!

RE @sonofevil: were you using one of the beta build I posted above? If so there was definitely a "widgets reset" issue between the first beta and subsequent builds, sorry :(

If you used the previous beta build, your widget settings may not come across due to updates to the database layout (re-importing your old backup should recover them). If you haven't used the previous beta build, the release candidate will migrate all your settings automatically.

Hanif1601 changed the title ~~Tabliss resets to default when my browsers opened~~ Tabliss resets to default settings on Microsoft Edge, Google Chrome, and Brave Jul 26, 2020

Hanif1601 changed the title ~~Tabliss resets to default settings on Microsoft Edge, Google Chrome, and Brave~~ Tabliss resets to default settings on major browsers (including Chrome-based browsers & Firefox) Aug 12, 2020

CraftyDH mentioned this issue Aug 31, 2020

Settings Not Saving #284

Closed

joelshepherd mentioned this issue Feb 21, 2022

Storage layer rewrite #444

Merged

joelshepherd mentioned this issue Mar 4, 2022

Settings are reset after restaring my laptop #450

Closed

joelshepherd mentioned this issue Mar 11, 2022

Tabliss does not appear to be saving settings in Firefox #176

Closed

joelshepherd closed this as completed Mar 19, 2022

mbierman mentioned this issue Apr 1, 2022

Safari web version loses settings #472

Closed

Tabliss resets to default settings on major browsers (including Chrome-based browsers & Firefox) #268

Tabliss resets to default settings on major browsers (including Chrome-based browsers & Firefox) #268

Comments

Hanif1601 commented Jul 11, 2020

jcgaza commented Jul 29, 2020

Reboot-Codes commented Jul 31, 2020

julianatfg commented Aug 4, 2020

6RASi commented Aug 5, 2020

Hanif1601 commented Aug 5, 2020

trickypr commented Aug 6, 2020

julianatfg commented Aug 6, 2020 • edited Loading

trickypr commented Aug 6, 2020

PyvesB commented Aug 8, 2020

julianatfg commented Aug 9, 2020

ghost commented Aug 10, 2020 • edited by ghost Loading

trickypr commented Aug 10, 2020

julianatfg commented Aug 11, 2020

Hanif1601 commented Aug 12, 2020

jcgaza commented Aug 12, 2020

BalinGrant commented Aug 22, 2020 • edited Loading

trickypr commented Aug 22, 2020

julianatfg commented Aug 22, 2020

julianatfg commented Aug 29, 2020 • edited Loading

Hanif1601 commented Aug 30, 2020

trickypr commented Aug 30, 2020

julianatfg commented Aug 30, 2020

trmdi commented Sep 4, 2020

Hanif1601 commented Sep 21, 2020

afcady commented Oct 11, 2020

trmdi commented Oct 17, 2020 • edited Loading

PaMaBa1806 commented Nov 3, 2020

trickypr commented Jan 7, 2022 • edited Loading

Gitoffthelawn commented Jan 7, 2022

trickypr commented Jan 7, 2022

ToddIndry37 commented Jan 7, 2022

joelshepherd commented Jan 7, 2022

Gitoffthelawn commented Jan 7, 2022

ToddIndry37 commented Jan 9, 2022

Xoouu commented Jan 9, 2022

ToddIndry37 commented Jan 9, 2022

ToddIndry37 commented Jan 9, 2022

joelshepherd commented Feb 8, 2022

ToddIndry37 commented Feb 8, 2022

joelshepherd commented Feb 8, 2022

joelshepherd commented Feb 12, 2022

julianatfg commented Feb 13, 2022

soumyaDghosh commented Feb 18, 2022

trmdi commented Feb 18, 2022

joelshepherd commented Mar 9, 2022

julianatfg commented Mar 9, 2022

Gitoffthelawn commented Mar 11, 2022 • edited Loading

mbierman commented Mar 11, 2022

joelshepherd commented Mar 12, 2022

sonofevil commented Mar 14, 2022 • edited Loading

mbierman commented Mar 14, 2022 • edited Loading

joelshepherd commented Mar 19, 2022

julianatfg commented Aug 6, 2020 •

edited

Loading

ghost commented Aug 10, 2020 •

edited by ghost

Loading

BalinGrant commented Aug 22, 2020 •

edited

Loading

julianatfg commented Aug 29, 2020 •

edited

Loading

trmdi commented Oct 17, 2020 •

edited

Loading

trickypr commented Jan 7, 2022 •

edited

Loading

Gitoffthelawn commented Mar 11, 2022 •

edited

Loading

sonofevil commented Mar 14, 2022 •

edited

Loading

mbierman commented Mar 14, 2022 •

edited

Loading