As well as being able to use a classic \u201chttp:\/\/domain.com\u201d style origin, widgets can also use a custom scheme called the Widget URI scheme that typically looks like this:<\/p>\n
The widget URI scheme<\/a> works like a \u201cfake\u201d HTTP server: sending back local files from inside a widget package (e.g., an image) by simulating a HTTP responses.<\/p>\n The misconception about origin arises because people don\u2019t really understand what an origin is: they think it means http:\/\/some.url.com (i.e., a website). Thankfully, the HTML Standard<\/a> makes it clear by defining an origin as:<\/p>\n In other words, widget:\/\/ makes for a perfectly valid origin.<\/p>\n Other posts in this series:<\/p>\n As well as being able to use a classic \u201chttp:\/\/domain.com\u201d style origin, widgets can also use a custom scheme called the Widget URI scheme that typically looks like this: widget:\/\/c1[\u2026UUID\u2026]a66\/index.html The widget URI scheme works like a \u201cfake\u201d HTTP server: … Continue reading widget:\/\/c1[\u2026UUID\u2026]a66\/index.html<\/code><\/p>\nopaque identifiers or tuples consisting of a scheme component, a host component, a port component, and optionally extra data.<\/q><\/p><\/blockquote>\n
\n