search

proginosko / LeechBlockNG-chrome

LeechBlock NG (Next Generation) for Chrome is a simple productivity tool designed to block those time-wasting sites that can suck the life out of your working day. All you need to do is specify which sites to block and when to block them.
https://www.proginosko.com/leechblock/
Mozilla Public License 2.0
74 stars 14 forks source link

Countdown Timer Inconsistent in Chrome #30

Closed ruffian706 closed 3 years ago

ruffian706 commented 3 years ago

Chrome v. 89.0.4389.90 LeechBlock v. 1.0.11.2 Mac OS 10.14.6

When I first load a site subject to blocking, the timer does not appear at the top of the browser window. If I switch to a different tab and then switch back, the timer appears, however it is not counting down. I cannot figure out when and whether the countdown is actually functioning behind the scenes and just not visually updating, or when the countdown timer is not counting down at all. For example, if I refresh the page (again the timer does not appear, and I have to switch to a different tab and then back to see it), sometimes it shows that time has elapsed and sometimes it does not; when it does show that time has elapsed, it is usually not on par with how much time should have elapsed. I do not get blocked when the time should be expiring, even if I refresh the page or load it new in a different tab. At some point it does decide to kick in and block if I refresh or reopen the page, but I haven't figured out when or why.

My setup may be slightly unusual in that in some cases I have the same sites in multiple blocking groups. E.g., In Group 1 I have a set of sites that I limit to 30 minutes every 8 hours during the workday, and in Group 2 I have larger set of sites (which includes those in Group 1) that I block altogether for a certain number of hours. However, the buggy functionality is not limited to those sites that overlap. E.g., sites in a completely unrelated Group 3, which is entirely unique to any other group, show the same behavior.

I have had this same setup (i.e., the overlapping sets in different groups) for quite some time (at least several months), and it worked fine. I began seeing these issues a couple weeks ago. Unfortunately Chrome and LeechBlock are set to autoupdate, so I do not know if the appearance of this behavior corresponded with a particular release of either.

ruffian706 commented 3 years ago

I'm leaving this up for posterity's sake. I thought I had uninstalled and reinstalled LeechBlock prior to posting this, but perhaps I had not. I did so (again?) and now it works fine.