Browser addon support seems has issue

[SettingDust]

Describe the bug
There isn't content in unknown project. But the time is recorded

How is it show in wakatime

System information
Please provide information on:

• Wakapi version: docker latest tag. Should be 2.7.0 that I've tried pull and up to date
  • If Docker: which image and tag? https://github.com/muety/wakapi/pkgs/container/wakapi
• Database (SQLite, MySQL, ... ?) postgres:12.3

[muety]

Hi @SettingDust, thanks for reporting this. Unfortunately, I can't really reproduce this. Seems to be working for me:

Can you tell which version of the browser plugin you are using and potentially even show your config (with API key redacted)?

[SettingDust]

Firefox. Addon 3.0.12.

[SettingDust]

And there is an error

[SettingDust]

MB. After look into the addon console. Caused by CORS. Seems the addon haven't grant the permission for the host. Should be reported to addon repo

But why is there time recorded

[muety]

The original WakaTime browser add-on does only have permissions for wakatime.com. The issue was discussed in #237, as a result of which we developed chrome-wakapi which (a) also has permissions for wakapi.dev and (b) allows to relay heartbeats to any other host (e.g. wakapi.example.org) through the official Wakapi instance, so no additional host permission are required for self-hosted instances.

However, it of course only works for publicly accessible instance, you won't be able to reach localhost this way. If you want the add-on to send data to localhost, there's no way around building the plugin yourself with custom host permissions compiled in.

But why is there time recorded

Could be coincidence? Are you using Wakapi with any other plugins (e.g. VSCode, IntelliJ, etc.)? If yes, probably one of them has sent heartbeats for "unknown" project.

[SettingDust]

Well. Grant permission should be a feature for the addon

[muety]

Permissions must be defined at compile time via host_permissions in the manifest.json file. That's a requirement of the WebExtension API and adds to security. In my understanding, there's no way to retroactively allow an add-on to make requests to hosts that were not specified in the manifest. The whole discussion in #237 is around just that. Please correct me if I'm wrong.

[SettingDust]

https://github.com/SettingDust/obsidian-web-clipper/blob/main/src/app/options/general/general.component.ts#L46-L52

Can grant permission with this

EDIT: Need add to optional section in manifest

[muety]

Very cool, didn't know that! I filed an issue with the official plugin, see wakatime/browser-wakatime#209. Maybe we can even get rid of chrome-wakapi in the long run.

[muety]

wakatime/browser-wakatime#221