We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Why doesn't firefox obey rel="icon" and instead assumes that /favicon.ico exists?

more options

We have a page where we just added <link rel="icon" type="image/ico" href="/other-path/favicon.ico"/> to the header, but while Firefox reads that link and includes the information in the page (can see in "View Page Info" -> Media), the .ico file specified is overridden by Firefox assuming that <page-path>/favicon.ico is where it should find the favicon. Is this the expected behavior? Every other browser follows this pattern, but Firefox does not (since at least Firefox 39 when I did some testing). Should I write this up in bugzilla?

We have a page where we just added <link rel="icon" type="image/ico" href="/other-path/favicon.ico"/> to the header, but while Firefox reads that link and includes the information in the page (can see in "View Page Info" -> Media), the .ico file specified is overridden by Firefox assuming that <page-path>/favicon.ico is where it should find the favicon. Is this the expected behavior? Every other browser follows this pattern, but Firefox does not (since at least Firefox 39 when I did some testing). Should I write this up in bugzilla?

Wšě wotmołwy (1)

more options

Rick said

Should I write this up in bugzilla?

Hi Rick, it's worth taking a look in Bugzilla to see whether it has been filed. Sometimes the search done when you start submitting a new bug is more accurate than the regular search box.

If you have a link to a page demonstrating this problem, that might also help.