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

[Bug 12365] Add @fullsize to <img>

From: <bugzilla@jessica.w3.org>
Date: Fri, 25 Mar 2011 02:08:43 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Q2wSB-0001MX-IW@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12365

--- Comment #9 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-03-25 02:08:41 UTC ---
(In reply to comment #7)
> I recall Mark Pilgrim was "looking at your, Wikipedia", for misuse of
> @longdesc. Did you use @longdesc as you described above?

Old versions of MediaWiki used longdesc to point at the image description page
(not the larger image version).  That was years ago, though.

(In reply to comment #8)
> * we look for attribute with *semantics* as primary effect. 

Wrong approach.  Start with use-cases, not semantics for the sake of semantics.
 Question one is, what features do you want users to have that they don't have
now?  Question two is, how do you best achieve that?  Do not try to ask
question two until you've gotten question one clearly answered.

> * the effect should be to express that, when it is used, then @src can be
> treeated (by users, search engines, browsers themselves etc) as a preview image
> for the image inside the new @foo attribute.

Not a use-case.  What problem exists that this is solving?  Why would anyone
want this, concretely?

> * My primary use case is "image galleries". Gallery is a wide term. The
> thumbnail alike examples of Wikipedia is one example of galleries - I agree! 
> But in Wikipedia's case, the fullsize (for lack of a better name) image is
> located at another "page". Whereas often, in javascript image galleries, the
> fullsize image is displayed in a display area on the same page. I hope, of
> course, that the attribute could work in both situations.

This is not a use-case, because it doesn't describe what the problem is. 
You're saying *how* the feature should be used, not *why* anyone would want to
use it.  Concretely, in terms of tangible benefits to my users, what would I as
an author gain from using this attribute?

> * Galleries create user expectations: they expect to get a beter - or alternate
> - quality image when they click the image. Thus they understand that the
> current image is a preview of some sort. 

If your use-case requires users to click on the images, why does <a> not
satisfy the use-case?

> * One effect that one could perhaps get could be that the @fullsize images were
> preloaded so the larger image could be displayed faster.  

Why does rel=prefetch not satisfy this use-case?


If you intend the editor or the Working Group to take your proposal seriously,
I strongly suggest you start with the description of a problem, and only then
suggest a feature to solve the problem.  The focus needs to be on the problem
(use-cases), not the solution.  I gave two good use-cases in comment 6.  Note
that both of them focus on specific user-visible benefits that authors cannot
easily attain without this new feature.

-- 
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 Friday, 25 March 2011 02:08:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 25 March 2011 02:08:53 GMT