In bug 1695247 we started collecting data on errors in network loads. The top DTD error loads in Beta are: * `omni.ja!/chrome/toolkit/content/global/DTD/xhtml1-strict.dtd` * `omni.ja!/chrome/devtools/content/memory/DTD/xhtml1-strict.dtd` Scanning our source we can see a number of relative paths in XHTML documents: https://searchfox.org/mozilla-central/search?q=DTD%2Fxhtml1-strict.dtd&path=&case=true®exp=false In particular the `devtools/client/memory/index.xhtml` seems like it could lead to the second of the loads (`/memory/` in the path). We should turn them into absolute URLs and maybe also be more vocal about broken DTD loads in browser console.
Bug 1695253 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
In bug 1695247 we started collecting data on errors in network loads. The top DTD error loads in Beta are: * `omni.ja!/chrome/toolkit/content/global/DTD/xhtml1-strict.dtd` (Beta: volume: 3,776/day, clients: 3,214/day) * `omni.ja!/chrome/devtools/content/memory/DTD/xhtml1-strict.dtd`(Beta: volume: 1,482/day, clients: 1,424/day) Scanning our source we can see a number of relative paths in XHTML documents: https://searchfox.org/mozilla-central/search?q=DTD%2Fxhtml1-strict.dtd&path=&case=true®exp=false In particular the `devtools/client/memory/index.xhtml` seems like it could lead to the second of the loads (`/memory/` in the path). We should turn them into absolute URLs and maybe also be more vocal about broken DTD loads in browser console.
In bug 1695247 we started collecting data on errors in network loads. The top DTD error loads in Beta are: * `omni.ja!/chrome/toolkit/content/global/DTD/xhtml1-strict.dtd` (Beta: volume: 3,776/day, clients: 3,214/day) * `omni.ja!/chrome/devtools/content/memory/DTD/xhtml1-strict.dtd`(Beta: volume: 1,482/day, clients: 1,424/day) Scanning our source we can see a number of relative paths in XHTML documents: https://searchfox.org/mozilla-central/search?q=%22DTD%2Fxhtml1-strict.dtd&case=true&path= In particular the `devtools/client/memory/index.xhtml` seems like it could lead to the second of the loads (`/memory/` in the path). We should turn them into absolute URLs and maybe also be more vocal about broken DTD loads in browser console.