18258 2012-07-18 17:51:55 +0000 Image inputs with no image should fall back to non-replaced elements, just like normal images 2013-01-07 07:03:37 +0000 1 1 1 Unclassified HTML.next default unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#images P3 normal --- 1 contributor silviapfeiffer1 bzbarsky mike public-html-admin public-html-wg-issue-tracking robin silviapfeiffer1 public-html-bugzilla oldest_to_newest 70982 0 contributor 2012-07-18 17:51:55 +0000 This was was cloned from bug 17630 as part of operation convergence. Originally filed: 2012-06-28 14:48:00 +0000 ================================================================================ #0 contributor@whatwg.org 2012-06-28 14:48:23 +0000 -------------------------------------------------------------------------------- Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/rendering.html Multipage: http://www.whatwg.org/C#images Complete: http://www.whatwg.org/c#images Comment: Image inputs with no image should fall back to non-replaced elements, just like normal images Posted from: 98.110.194.72 by bzbarsky@mit.edu User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/16.0 Firefox/16.0 ================================================================================ #1 Boris Zbarsky 2012-06-28 14:52:20 +0000 -------------------------------------------------------------------------------- And in particular, the text in the spec makes it very likely that the alt text will be cut off. The difference from normal image behavior seems pretty unnecessary and confusing. ================================================================================ 80984 1 silviapfeiffer1 2013-01-07 07:03:37 +0000 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-v2.html Status: Partially Accepted Change Description: https://github.com/w3c/html/commit/cdca4f77dba672331c25467d18c27371757fef01 Rationale: moving to HTML5.1 and adopting WHATWG patch; see continuing discussion at https://www.w3.org/Bugs/Public/show_bug.cgi?id=17630 - will apply any further outcomes from that bug, but for now closing it