It's not part of individual directories. That would be stupid.
Having a path-specific favicon actually sounds like a feature.
Having a path-specific favicon actually sounds like a feature.
https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes...
Can you provide at least a couple of use-cases for a path specific favicons?
<meta favicon=./user_favicon.ico>
Do this require a browser probing every path with /favicon.ico?
I understand what you tried to retort just to retort, but I've had asked for the actual use-cases, not the mock ones and purely hypothetical.
The use case is this: I drop the icon in a folder and never look back. It just works. Why would I want an additional approach?
> These can be solved by
> <meta favicon=./user_favicon.ico>
> or something.
There is nothing to solve, it already works, the line has no advantages but it does have "or something" disadvantages.
Your memory is no doubt better than mine but you didn't remember how the tag worked. <meta> is for information about the document <link> is to describe relationships with other things. You've also left out the quotes.
<link rel="icon" type="image/x-icon" href="/favicon.ico">
For fun someone thought it a good idea to also have rel="shortcut icon" I'm picturing a room full of applauding people. (Who had nothing better to do)
image/x-icon isn't really correct, x- is for experiment, it should be type="image/vnd.microsoft.icon"
Browsers accept anything in the attribute. They also support not having a type. But if our goal is to have superfluous lines of html we should definitely go with the correct IANA mime type registered in 2003.
Redundant link headers also sounds fun!
Maybe in the future there will be new fixes for problems no one has?
Is that also the correct behavior for trying to identify a favicon for something like docs.oracle.com/javase/8/docs/api/org/xml/sax/helpers/DefaultHandler.html
Though they aren't common enough that it needs to be a built-in, especially as you can already specify a page specific icon via a link tag in your page's head which every up-to-date stable browser has had support for since 2010 or before (ref: https://caniuse.com/?search=link-icon).
Can I see them?
Generally: Any circumstance where you might want the icon to change per section/page/app rather than per (sub)domain. Do you want me to enumerate all possible combinations of web server configuration and tick the ones that applies to?!
For one: perhaps you host several tools off the same domain name, either literally on the same web server or via a proxy arrangement. As I said, these circumstances aren't all that common, and when they turn up I doubt the right favicon being use is going to be something you'd care about overly, but I wouldn't be surprised to find there are circumstances where it is important enough to someone.