Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Starred by 224 users
Status: Duplicate
Merged: issue 368830
Owner:
Closed: Jul 2014
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Launch-OWP
Launch-Accessibility: ----
Launch-Legal: ----
Launch-M-Approved: ----
Launch-M-Target: ----
Launch-Privacy: ----
Launch-Security: ----
Launch-Status: ----
Launch-Test: ----
Launch-UI: ----
Product-Review: ----



Sign in to add a comment
Add support for the picture element
Project Member Reported by y...@yoav.ws, Apr 19 2013 Back to list
(See go/owp-launch-guide for an overview)

Change description:
Enable a responsive images solution and give developers control over the image resource that is downloaded & displayed using the various resources' media attributes

Changes to API surface:
* The `picture` element will be recognized in HTML and displayed as an image. 
* Its `src` attribute will trigger a resource download. 
* The `src` attribute of the first matching `source` child element with a matching `media` attribute will trigger a resource download, unless `picture`has an `src` attribute.
* The DOM API for the element will resemble that of `img`, with possible minor changes.

WebKit bug: None

Public standards discussion: http://www.w3.org/TR/html-picture-element/

Support in other browsers: current (expected)
Internet Explorer:
Firefox:
Safari:
Opera:

*Make sure to fill in any labels with a -?, including all OSes this change
affects. Feel free to leave other labels at the defaults.
 
This is redundant with <img srcset>, which is simpler to implement and use.
Ian,

Thanks for posting. Of course your opinion on the subject is certainly valued and appreciated, and has led to refinements in both the use cases and `picture`/`srcset` specifications. However, there is a healthy amount of data showing that the two markup patterns best address different use cases [1], and can be used either independently or in concert [2]. While `srcset` may be simpler to implement it has been shown that authors prefer the `picture` syntax by a wide margin, most recently in the results of a poll [3] openly distributed via Twitter.

Just to sum up: the two syntaxes are complementary, not diametrically opposed. We believe each are stronger when used in concert, and that there is a valid case for `picture`’s implementation.


1: http://www.w3.org/TR/2013/WD-respimg-usecases-20130226/
2: http://www.w3.org/TR/2013/WD-html-picture-element-20130226/#relationship-to-srcset
3: https://docs.google.com/forms/d/1LIbd9wiM7M_m-rUB85WAiGT-h8QUY-PRJwjiBRiuY4Y/viewanalytics
Comment 3 Deleted
Comment 4 by y...@yoav.ws, May 29 2013
Please avoid non-technical comments on this thread. 
If you're here to show support for the feature (which is awesome!), you can star this issue which will both show your support and keep you notified on any future developments. 
"+1" type of comments are in general not helpful in this type of threads.
Comment 5 by rbyers@chromium.org, Sep 24 2013
Owner: y...@yoav.ws
Project Member Comment 6 by bugdroid1@chromium.org, May 23 2014
The following revision refers to this bug:
  http://src.chromium.org/viewvc/blink?view=rev&rev=174731

------------------------------------------------------------------
r174731 | cbiesinger@chromium.org | 2014-05-23T23:19:51.015885Z

Changed paths:
   M http://src.chromium.org/viewvc/blink/trunk/Source/core/html/HTMLPictureElement.h?r1=174731&r2=174730&pathrev=174731
   M http://src.chromium.org/viewvc/blink/trunk/Source/core/html/HTMLSourceElement.cpp?r1=174731&r2=174730&pathrev=174731
   M http://src.chromium.org/viewvc/blink/trunk/Source/core/html/HTMLImageElement.cpp?r1=174731&r2=174730&pathrev=174731
   A http://src.chromium.org/viewvc/blink/trunk/LayoutTests/fast/dom/HTMLImageElement/image-picture-source-dynamic-changes.html?r1=174731&r2=174730&pathrev=174731
   M http://src.chromium.org/viewvc/blink/trunk/Source/core/html/HTMLSourceElement.h?r1=174731&r2=174730&pathrev=174731
   M http://src.chromium.org/viewvc/blink/trunk/Source/core/html/HTMLImageElement.h?r1=174731&r2=174730&pathrev=174731
   M http://src.chromium.org/viewvc/blink/trunk/Source/core/html/HTMLPictureElement.cpp?r1=174731&r2=174730&pathrev=174731
   A http://src.chromium.org/viewvc/blink/trunk/LayoutTests/fast/dom/HTMLImageElement/image-picture-source-dynamic-changes-expected.txt?r1=174731&r2=174730&pathrev=174731

<picture>: Update the <img> element when a <source> changes

R=abarth@chromium.org
CC=yoav@yoav.ws
BUG= 233751 

Review URL: https://codereview.chromium.org/290203002
-----------------------------------------------------------------
Comment 7 by y...@yoav.ws, Jul 23 2014
Mergedinto: 368830
Status: Duplicate
This is a duplicate of https://code.google.com/p/chromium/issues/detail?id=368830 which is now fixed
Sign in to add a comment