- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Mon, 25 Oct 2010 17:56:40 -0700
- To: Jonas Sicking <jonas@sicking.cc>
- Cc: Anne van Kesteren <annevk@opera.com>, Arun Ranganathan <arun@mozilla.com>, public-webapps <public-webapps@w3.org>, Arthur Barstow <art.barstow@nokia.com>, Adam Barth <abarth@gmail.com>, Darin Fisher <darin@google.com>
On Mon, Oct 25, 2010 at 5:51 PM, Jonas Sicking <jonas@sicking.cc> wrote: > On Mon, Oct 25, 2010 at 5:04 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote: >> On Mon, Oct 25, 2010 at 4:48 PM, Jonas Sicking <jonas@sicking.cc> wrote: >>> Like I said, I think creating an OM that covers all the cases here >>> would create something very complex. I'd love to see a useful proposal >>> for <http://dev.w3.org/csswg/css3-images/>. >> >> It doesn't seem overly difficult. Using the proposed Values API, >> you'd do something like "elem.style.values.backgroundImage.url = >> [DOMURL goes here]". > > That doesn't cover nearly all the ways you can use URLs as defined in > http://dev.w3.org/csswg/css3-images/ which support multiple levels of > fallback images, with snapping and resolution as well as gradients and > fallback colors. And with used in a property like backgroundImage, you > can have several combined instances of those. Consider: > > style="background-image: image(sun.svg, 'sun.png' snap 150dpi), > image(wavy.svg, 'wavy.png' 150dpi, 'wavy.gif', radial-gradient(...))" This would be part of the <url> interface, and would be accepted anywhere a <url> is currently accepted. Exposing the correct interface of function arguments would be a job for the function interface in the Values API, and is designed to be orthogonal. ~TJ
Received on Tuesday, 26 October 2010 00:57:33 UTC