This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 20173 - No way to determine which source is being displayed
Summary: No way to determine which source is being displayed
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: The srcset attribute (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Edward O'Connor
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 20210 20256
  Show dependency treegraph
 
Reported: 2012-11-30 15:15 UTC by Marcos Caceres
Modified: 2013-01-24 20:06 UTC (History)
4 users (show)

See Also:


Attachments

Description Marcos Caceres 2012-11-30 15:15:45 UTC
The img@srcset spec lacks a script-based means to determine what resource the image element is displaying (if any). The use case for this is for testing and generally for a developer to know what is going on.
See: http://usecases.responsiveimages.org/#api-to-manipulate-sources
Comment 1 Edward O'Connor 2013-01-24 19:53:14 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the Editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the Tracker Issue; or you may create a Tracker Issue
yourself, if you are able to do so. For more details, see this document:

   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Additional Information Needed
Change Description: No change.
Rationale: As Ian said in bug 20210, the stated use case could be
addressed by feature additions to browsers' developer tools. Is there a
use case that requires this information be exposed to Web content?
Comment 2 Marcos Caceres 2013-01-24 20:06:53 UTC
the RICG could not come up with any.