W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > May 2011

[Bug 12365] Add @fullsize to <img>

From: <bugzilla@jessica.w3.org>
Date: Sun, 08 May 2011 03:55:58 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QIv66-0007p5-Nz@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12365

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |WONTFIX

--- Comment #11 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-05-08 03:55:56 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: Rejected
Change Description: no spec change
Rationale: There are a variety of ways to do this already:

 <a href="big.jpeg" rel="..."><img src="thumbnail.jpeg" alt="textual
replacement"></a>

 <img src="thumbnail.jpeg" data-fullsize="big.jpeg" alt="textual replacement">

 <figure>
  <figcaption><a href="big.jpeg" rel="...">caption</a></figcaption>
  <img src="thumbnail.jpeg" alt="textual replacement">
 </figure>

 <object data="thumbnail.jpeg"><object data="big.jpeg">textual
replacement</object></object>

 <details>
  <summary><img src="thumbnail.jpeg" alt="brief textual replacement"></summary>
  <img src="big.jpeg alt="detailed textual replacement">
 </details>

(The rel="..." values would be new values.)

If there's a problem to solve here, we should just pave a cowpath. If there's
no cowpath to pave, then it probably isn't a problem people are really having.
As far as I can tell, there's indeed not really a cowpath to pave. (Note that
just making an element available does not magically mean everyone will use it,
so if the problem is that people are not using a standard feature to do this,
merely providing one may not solve the problem.)

If the problem is just that there's nowhere to put script-specific data, that's
what the new data-*="" attributes are for, so that problem is solved.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Sunday, 8 May 2011 03:56:00 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:09 UTC