Resources from different origin but same protocol should load

[Gozala]

Several issue were reported that seem to prevent embedding or loading content from same protocol but a different origin:

• Document <img src="dweb://html/dot.svg" /> does load image if loading document URL has different origin e.g. dweb://foo/ (For details see Protocol Handler: SVG does not render when used in img HTML tag #54)
• Document like <video src="dweb://html/video.webm" /> does not load video if loading document URL has different origin e.g. dweb://foo/ (For details see Protocol Handler: WEBM does not load when used in video HTML tag #57)
• Link like <a href="dweb://async">async</a> does not load when clicked if document URL has different origin e.g. dweb://hello/ (For details see [WIP] Add links to default dweb page in protocol example #62)

[lidel]

Clarification for drive-by visitors: this issue is about step 4 from quoted issue.

A better illustration of the issue (red == load failed):

[Gozala]

Just tested and #69 does fix dweb://foo/ example that embeds <img src="dweb://html/dot.svg" />. Will confirm video next.

[Gozala]

Also quoting issue pointed out in #62 by @willemneal here, which is caused by the same issue

Currently dweb links don't have an effect. I'm sure this would work by registering an on click function for each link, but I thought it would just work with <a href="dweb://async">async</a> since it works with other protocols.

[Gozala]

Verified that #69 also addresses example with embedded video.

[lidel]

Just confirmed it works as expected, thank you!