You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Operating system or device, Godot version, GPU Model and driver (if graphics related):
Firefox 57 and Chromium 62 under Archlinux 64bits, Godot compiled today 33ffdba and WebAssembly template idem
Issue description:
This can be done manually, but it would be great if Godot could export automatically the project icon as a favicon in HTML5.
I know this was partially answered in #12543:
We need ability for users to add a custom icon for their executable, not have to rely on resource hacker
Problem with this is that it seems to be only doable when exporting from Windows. Cant be done from other platforms. All libraries we tried to do this ended up corrupting the executable.
but as far as I understand this do not apply to HTML5 because it's not about writing it to an executable, but a matter of copying the .png file, renaming to favicon.png, and linking in the HTML file.
For now, the debug console in the browser is complaining about icon missing:
akien-mga
changed the title
[Wishlist] Project icon as favicon in HTML5 WebAssembly export
Project icon as favicon in HTML5 WebAssembly export
Nov 20, 2017
Operating system or device, Godot version, GPU Model and driver (if graphics related):
Firefox 57 and Chromium 62 under Archlinux 64bits, Godot compiled today 33ffdba and WebAssembly template idem
Issue description:
This can be done manually, but it would be great if Godot could export automatically the project icon as a favicon in HTML5.
I know this was partially answered in #12543:
but as far as I understand this do not apply to HTML5 because it's not about writing it to an executable, but a matter of copying the .png file, renaming to favicon.png, and linking in the HTML file.
For now, the debug console in the browser is complaining about icon missing:
Thanks for your answer and work !
The text was updated successfully, but these errors were encountered: