Only hide thumbnails during set timeframe

[IsaiahPapa]

If work mode is enabled:

• If it's current work time, hide/blur/etc thumbnails.
• If it's not work time, show thumbnails/disable extension

if work mode is disabled:

• Extension acts normally

Added "work mode" ability to only hide thumbnails during a set timeframe. Disabled by default, default time frame from 9am-5pm.

Please check the updateElem function, because I overrode the main functionality and would be open to a better way.

[domdomegg]

Question: Should this be part of the extension?

tldr: Yes. It's in keeping with a key use case, and the downsides are not too great.

For:

• A primary use case of the extension is to improve productivity by reducing distractions. This feature ties in well with this use case, as users might want to set certain hours of the day for work / study / etc. and others where they're free to do what they want. Software that shares characteristics often have time-based blocking, e.g. LeechBlock).
• We could deprecate and remove this functionality later if it does become confusing to users or is a pain to maintain.
• The code changes don't look too significant, and it's therefore not that much to maintain.

Against:

• More functionality can confuse users as to the purpose of the extension. Additionally, it can confuse users and result in users misconfiguring the extension. We can mitigate this somewhat by ensuring the options menu is still clear.
• Adding features results in increased code complexity and maintenance burden. We can mitigate this by ensuring the code is simple and in keeping with the existing logic.

Alternatives:

• Directing users to manually enable and disable the extension. This is unsuitable as the point of the extension is to make it easy for users to control distractions automatically. Having to manually enable this is will make people less likely to use the extension and get value from it.
• Encouraging users to use another tool to enable/disable the extension at particular times. After a very brief search, I was unable to find a solution to easily enable/disable extensions automatically in a scheduled way.

[domdomegg]

Looks pretty good! A few changes requested, but concept is sound and most code good.

If you're busy, am happy to make the edits myself in the next couple of days.

Review comments key

[domdomegg]

should: call this scheduledBlocking or timeBasedBlocking, or similar. On first glance I don't think I'd know what workMode means.

[domdomegg]

must: Update the typedef on lines 9-18 to match (GitHub won't let me comment there). This ensures intellisense works as expected, and in future if we convert to TypeScript / run linters they'll pass.

You probably will want to merge in the master branch first, because I think there may be a few merge conflicts otherwise.

[domdomegg]

consider: store this as an array of enabled times. This would allow users to set multiple periods where the extension is enabled, for example if they have a break in their work day or similar.

We don't actually have to accept more than one to start with, but I think it'd be good to design this so that if we do want to accept more than one in future people don't lose their settings. The options page would either:

• have an input as just a text field, where people can enter comma-separated ranges - format could be like LeechBlock (e.g. 0900-1700,1800-1900) or ISO8601-like format (e.g. 09:00/17:00,18:00/19:00)
• have pairs of time inputs, and users could click a + icon to add more ranges

[domdomegg]

must: I think we can move this logic into the isDisabled check. For example, adding a condition like:

    || (options.workMode.enabled && !IsItWorkTime(options.workMode.startTime, options.workMode.endTime))

This significantly reduces code duplication and complexity.

[domdomegg]

nit: use camel case for JS functions. Align naming with options if we're renaming to scheduledBlocking.

[domdomegg]

praise: This logic looks sound and simple. I like it!

[domdomegg]

praise: I like the use of the type="time" input!

[domdomegg]

(update naming here if we're changing it to scheduledBlocking or similar)

[domdomegg]

consider: Adding the strings to the en and es translation files in _locales. This makes things easier to translate in future.