BelKed
BelKed
If you have the color set correctly like this, it's very likely a bug then...
Good point, "inverting" the colors makes it look amazing 😍
I can reproduce this "bug" on the same OS and version. The cause of this "bug" is the usage of another windows watching strategy implemented in `0.12.1` (https://github.com/ActivityWatch/aw-watcher-window/commit/fc423c1d95e65b269e23d9f424fc7bfc38777e52, https://github.com/ActivityWatch/aw-watcher-window/commit/6d68ae35353bd43e8f0c7235a2a613dcfb272c17).
The problem is not that there are buckets with an unknown `hostname`, but that `unknown` is selected as the hostname in the **Category Builder** options. --- For me, however, it...
@cweiske Btw, the advice to delete all buckets with `unknown` hostname is not an ideal solution, since people may lose their data from web watchers (`< 0.5.0`), editor watchers, etc.
@AGoldenDragon Please open a new issue describing your problem as accurately as possible :)
Since the data ends in the `aw-watcher-web-chrome` bucket, the problem is the same as it was with the Brave Browser: https://github.com/ActivityWatch/activitywatch/issues/461
The problem with these "non-mainstream" browsers is that they can't be distinguished from their upstream unmodified versions — so Vivaldi is disguised as Firefox, and Arc is disguised as Chrome....
No, Firefox does not expose the same Apple Events APIs for accessing tab and window information like Chrome and Safari do on macOS. This is why we have to use...
- Fixed in https://github.com/ActivityWatch/aw-watcher-web/pull/154