Hi sir, My name is Natnael Yohanes 3rd Year Software engineering Student at AAiT(Ethiopia). I am a Full-stack developer specifically MERN stack and came to SugarLabs to contribute with the skills I have.
Could you assign me to this one?

I have checked line 14 and if the logoID is undefined or corresponds to an invalid image, the favicon will fail to load.
But it does not necessarily impact the live site negatively if the default favicon is functioning as a fallback
(i.e this is the default one <link id="defaultIcon1" rel="shortcut icon" href="{{ site.baseurl }}assets/favicon_06.png" />)
We can write an additional fallback code in JavaScript and also comment on the hardcoded URL.

I'm not certain that this ever effects the production site.

But I don't understand why we get the error when running it locally.

@pikurasa, can I work on this issue?

Should probably also change the defaultIcon href sooner, using script in index.html, as the way it is happening at the moment in js/main.js on Firefox collides in time with the loading of the default, resulting in NS_BINDING_ABORTED in Console and Network view of Developer Tools.

Hi @pikurasa @quozl,

I’ve submitted a PR (#617) to fix the "favicon not found" error on non-homepage pages, particularly on Firefox. The issue was caused by an incorrect favicon path, and the fix ensures consistent favicon display across all pages.
Please review the PR and let me know if any changes are needed.

Thanks. You don't need to tell us you've made a pull request for the issue, as GitHub automatically tells us.

Reproduced on master 66f7078. As indicated earlier, the problem continues to be collision between the asynchronous threads; the execution of the js/main.js vs the automatic loading of the icon by the pre-rendering of the index.html. Perhaps the defer in the call to js/main.js should be reconsidered?