- From: Marcos Caceres <w3c@marcosc.com>
- Date: Wed, 28 Nov 2012 00:32:33 +0000
- To: Miguel Garcia <magarcia2@me.com>
- Cc: Scott Jehl <scott@scottjehl.com>, "public-respimg@w3.org" <public-respimg@w3.org>
Agreed 100%, but we need to check for conflicts (as we are redefining how an attribute works). There must be a reason why video has both src and currentSrc? Irrespective, we need a strong use case. Sent from my iPhone On 28 Nov 2012, at 00:23, Miguel Garcia <magarcia2@me.com> wrote: > As would I. This behavior not only makes the most sense, it provides the greatest level of backward compatibility with current behavior. > > Miguel Garcia II > > On Nov 27, 2012, at 11:24 AM, Scott Jehl <scott@scottjehl.com> wrote: > >> I would expect the src property (not attribute) to return the current image source href. >> >> >> >> >> On Nov 27, 2012, at 10:56 AM, Marcos Caceres wrote: >> >>> Hi, >>> with the srcset attribute, there is currently no way for a developer to determine what the currently selected source is for an element. >>> >>> Apart from testing, can anyone thing of any good use cases for accessing the current source? >>> >>> If we can get some good use cases, then we make a case to add it a feature. >>> >>> What I envision is an IDL attribute that returns the resolved URL of the current source. >>> >>> so: >>> srcset="foo x2, bar 1x" >>> >>> Where foo is selected. Then, in JS: >>> >>> //read only >>> var url = element.currentSrc >>> >>> would return: "http://example.com/foo" >>> >>> I'm asking because Hixie said that the testing use case is not strong enough to warrant adding the above attribute to the srcset spec. To get the attribute added, we would need a strong use case(s) and backing from a browser vendor. >>> >>> Kind regards, >>> Marcos >>> -- >>> Marcos Caceres >
Received on Wednesday, 28 November 2012 00:33:03 UTC