On Sun, Oct 5, 2014 at 11:19 AM, Scott Miles wrote:
>> The URL is parsed again? That seems like something that should not
>> happen. Are you copying the node perhaps?
>
> There is no explicit copying, but I don't know if there is something
> implicit happening when the element goes trans-document.
> The URL is parsed again? That seems like something that should not
> happen. Are you copying the node perhaps?
There is no explicit copying, but I don't know if there is something
implicit happening when the element goes trans-document.
Sample code (assume index.html that imports import/import.
On Sat, Oct 4, 2014 at 7:00 PM, Scott Miles wrote:
> An issue is that a relative URL is only correct as long as the `img` (for
> example) is owned by the import. If you migrate the element to the main
> document, the path is now relative to the wrong base, and users are
> confused. One can do `img
An issue is that a relative URL is only correct as long as the `img` (for
example) is owned by the import. If you migrate the element to the main
document, the path is now relative to the wrong base, and users are
confused. One can do `img.src = img.src;` before migrating the node, and
that will fr
On Thu, Oct 2, 2014 at 3:09 PM, Anne van Kesteren wrote:
> This is a hard problem:
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=20976#c8
I saw you commented on the bug, but I prefer keeping that bug focused
on several other problems around base URLs so let's continue here. You
gave this exam
On Thu, Oct 2, 2014 at 2:59 PM, Mathias Bynens wrote:
> Thoughts?
This is a hard problem: https://www.w3.org/Bugs/Public/show_bug.cgi?id=20976#c8
--
https://annevankesteren.nl/
:
https://github.com/mathiasbynens/relative-urls-in-web-components/tree/gh-pages/packaged-web-component
Here’s an example (included in the component’s package) showing the component
in action:
https://mathiasbynens.github.io/relative-urls-in-web-components/packaged-web-component/example.html
It
