W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2019

Re: [csswg-drafts] [css-images][css-masking][paint] Ambiguities in handling url() (#383)

From: Dirk Schulze via GitHub <sysbot+gh@w3.org>
Date: Wed, 24 Jul 2019 06:41:22 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-514501920-1563950481-sysbot+gh@w3.org>
@tabatkins So now it is up to the UA to reload or reuse/reinterpret the resource depending on the UAs own requirements?

Also, agree with @rocallahan that we should load an element reference document with the same restrictions as an <image> and special case self referencing documents (only fragment identifier or URL that points to the same document) in general. That might be part of fetching and using an ambitious URL as <image> might imply it but IMO should be mentioned explicitly.

GitHub Notification of comment by dirkschulze
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/383#issuecomment-514501920 using your GitHub account
Received on Wednesday, 24 July 2019 06:41:23 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:50 UTC