It existed in mae's #33, but ozy was not satisfied with including a binary file identical to https://hakurei.app's favicon, and hence removed it. However, it's possible to explicitly specify the favicon with a link tag; provided a content security policy that isn't too strong, this should work fine.
It existed in mae's #33, but ozy was not satisfied with including a binary file identical to <https://hakurei.app>'s favicon, and hence removed it. However, it's possible to [explicitly specify the favicon] with a link tag; provided a content security policy that isn't too strong, this should work fine.
[explicitly specify the favicon]: https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Attributes/rel#icon
kat
requested review from cat 2026-05-15 18:52:56 +09:00
kat
marked the pull request as work in progress 2026-05-16 14:22:31 +09:00
kat
marked the pull request as ready for review 2026-05-17 18:42:33 +09:00
Nota bene: MDN notes something that I won't pretend to understand (CSPs are magic to me):
Note: The crossorigin attribute is not supported for rel="icon" in Chromium-based browsers. See the open Chromium issue.
To me that just means “try it in Chromium before merging”. I only have various Electrons, from which I can't easily test favicons, so @cat'll have to do that.
Nota bene: MDN notes something that I won't pretend to understand (CSPs are magic to me):
> <strong>Note</strong>: The [`crossorigin`](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Attributes/crossorigin) attribute is not supported for `rel="icon"` in Chromium-based browsers. See the [open Chromium issue](https://crbug.com/1121645).
To me that just means “try it in Chromium before merging”. I only have various Electrons, from which I can't easily test favicons, so @cat'll have to do that.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
It existed in mae's #33, but ozy was not satisfied with including a binary file identical to https://hakurei.app's favicon, and hence removed it. However, it's possible to explicitly specify the favicon with a link tag; provided a content security policy that isn't too strong, this should work fine.
Nota bene: MDN notes something that I won't pretend to understand (CSPs are magic to me):
To me that just means “try it in Chromium before merging”. I only have various Electrons, from which I can't easily test favicons, so @cat'll have to do that.
2a0d2301eato6f50811dc9LGTM