MicrosoftEdge / MicrosoftEdge/Demos
Console error favicon.png (localhost), & Failed to load resource
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 233
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 4
Description
Maybe only occurs on localhost, not gh.io.
Maybe my fork was behind, when seeing the old favico.png error in Console.
Encountered during creating PR #135 samples. Kept having to Clear Console Messages to make the Console tab clean, to get rid of an irrelevant error about favicon.png.
The issue repros in at least one of these samples (or, it did, in localhost):
https://github.com/MicrosoftEdge/Demos/pull/135 --
| New sample | Demo URL | favico.png error? |
|---|---|---|
| /at-rules-font-palette-values/ | https://microsoftedge.github.io/Demos/at-rules-font-palette-values/ | Failed to load resource: the server responded with a status of 404 () - this error went away after super refresh. |
| /at-rules-position-try/ | https://microsoftedge.github.io/Demos/at-rules-position-try/ | ok |
| /at-rules-property/ | https://microsoftedge.github.io/Demos/at-rules-property/ | ok |
| /at-rules-scope/ | https://microsoftedge.github.io/Demos/at-rules-scope/ | ok |
| /at-rules-supports/ | https://microsoftedge.github.io/Demos/at-rules-supports/ | ok |
| /cascade-layers/ | https://microsoftedge.github.io/Demos/cascade-layers/ | ok |
| /emulate-focused-page/ | https://microsoftedge.github.io/Demos/emulate-focused-page/ | ok |
| /highlight-pseudo-elements/ | https://microsoftedge.github.io/Demos/highlight-pseudo-elements/ | ok |
Screenshots showing various errors to fix in Console:
https://microsoftedge.github.io/Demos/at-rules-font-palette-values/
"Failed to load resource: the server responded with a status of 404 ()"
Error didn't occur after did:
In Edge, F12 (DevTools) > Right-click Refresh > Empty cache and hard refresh > F12.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the console error in the listed demo pages, especially at-rules-font-palette-values, using the local sample and the hosted URL for comparison. Inspect the page resources and confirm the finished change no longer produces a favicon.png 404 in the browser console after a normal refresh.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100