Conversation
|
Thank you, Travis. And now we have the same problem with restrictions. This is reproduced when we set the path in the list of constraints, for example, "github.com ", and then open the page with the URL "github.com/web-activity-time-tracker ". Perhaps we need to make a new flag in the list of restrictions indicating "the entire domain" and "Only the current page with all nested paths". This can work more accurately with a list of restrictions. What do you think ? |
|
Thanks for the feedback, let me take a look and try to understand the issue, because setting restrictions at the host level should still be working. |
|
It turns out this was caused by a pre-existing race condition, where |
Hi, Travis. |
Shouldn't it only be checking for the current tab? Maybe I'm not understanding, are you saying the expectation is that the timer will increment for tabs that are not active? So if I have two tabs open for different restricted Urls and I'm only active on one of them, the extension will increment the activity for each tab and ultimately block both, even if I never go to the other tab? |
Fixes two issues with restrictions:
Ideally, we would add a restriction icon for urls that are restricted by path as well, maybe this could be a future enhancement.