-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to deal with favicon? #650
Comments
A concrete example is the authentication portal which uses the new W3C style but at a different domain https://auth.w3.org/ @simonrjones any specific recommendation for favicon or can we simply add the above line to the website template? |
hi @vivienlacourba yes I agree that is worth adding. The example HTML added by @deniak looks perfect to me. If possible, can you add an icon for Apple, iOS uses a custom link rel type. Example:
|
Assigning to @deniak for implementation. |
Describe the issue
Nowadays, browsers systematically try to fetch a favicon when loading pages. If no icon link tag is provided (see below), then the browser try to look for one at the root of the website which may result in a 404 if it doesn't exists (might be the case for some sub domains).
The different templates in the design system don't include that icon link but it's probably good to add it even if the favicon exists at the root of w3.org. So even if the template is used outside www.w3.org (github.io, different subdomain, etc), we would still have the good W3C favicon.
The text was updated successfully, but these errors were encountered: