Cookie-autodelete: Change delay before cleaning resolution from minutes to seconds

[thomasrussellmurphy]

Change delay before cleaning resolution from minutes to seconds

The current implementation provides:

Enable Automatic Cleaning? Delay Before Cleaning: integer number entry Minute(s)

This results in a smallest setting resolution of 1 minute. The UI currently shows a red outline if you try to enter a decimal value (e.g. 1.5, 0.1). Can this setting be changed to use a resolution of seconds or settable seconds/minutes?

• OS/version: macOS 10.12.6
• Browser/version: FF 56.0.2
• Cookie AutoDelete version: 2.0.1

[TheRealestMVP]

According to the FAQ, this is intentional:

Why does the "delay before cleaning" default to 1 minute?

• Consistency. Chrome's Alarm API fires off only after a minute.
• Also, don't want to provide different defaults for different browsers since it is impossible since I have to test for each browser to see if the defaults stick (browser detection is not foolproof).

[thomasrussellmurphy]

So the _implied_ answer from the FAQ is Chrome only allows a resolution of 1 minute and, for consistence in the code base, allowing smaller resolution isn't supported?

I'm perfectly fine with the default. The default could be 30 minutes for all I care. I'm just after an improved (personal) UX in wanting a smaller unit of resolution available.

[practik]

No, smaller resolutions are supported. I have my delay set to 0.1 minute and my cookies get deleted after six seconds. Just ignore the red outline.

[thomasrussellmurphy]

Hmm. Indeed it seems that in FireFox 56.0.2 the delay can be set to fractional minutes and it works. This may just be a UI correction, then. It would be valuable to better understand what the current practical limitations are so that the UI might be able to be improved.

[ke-d]

This may just be a UI correction, then. It would be valuable to better understand what the current practical limitations are so that the UI might be able to be improved.

Yes, that was a problem that was caused by moving to the newest version of bootstrap in #180.

[ke-d]

I changed the delay from minutes to seconds in 5fd26736cd017a215295bc09cc497a7d70fd05e9 because I figured out a workaround for Chrome, which makes fixing the red outline unnecessary.

[ke-d]

Closing since 2.1.0 is out.

[thomasrussellmurphy]

Reverted title of issue for search accuracy and because there's still a red outline when a decimal value is entered. Now that outline reasonably indicates a non-optimal value entered in the field.