- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Apr 2017 05:52:22 +0000
- To: public-css-archive@w3.org
>The last resolution is the actual one That would be "RESOLVED: Let's stop resolving" ? ______________________ > For ambiguous cases, UAs SHOULD first see if there's an appropriate reference, otherwise go back and reload as an image So, does this mean that [my URL-resolution algorithm from SVG 2](https://www.w3.org/TR/SVG2/linking.html#processingURL-validity) is still valid? Although, now I read it again I realize that I should have been more clear that there are two cases for what to do if a target element can't be located, depending on whether it is a same-file vs different file references. - Same file: if the target element doesn't exist or is the wrong type, listen for DOM mutations in case the problem is fixed later. - Different file: if the target element doesn't exist or is the wrong type, and property can also accept an image, then re-process the referenced file as an image resource. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/383#issuecomment-296080508 using your GitHub account
Received on Friday, 21 April 2017 05:52:28 UTC