- From: <bugzilla@jessica.w3.org>
- Date: Wed, 03 Oct 2012 10:38:51 +0000
- To: public-html-a11y@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18384
Marcos Caceres <w3c@marcosc.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://www.w3.org/Bugs/Pub
| |lic/show_bug.cgi?id=18384
--- Comment #11 from Marcos Caceres <w3c@marcosc.com> 2012-10-03 10:38:51 UTC ---
(In reply to comment #10)
> Instead of trying to separately address this feature in HTML5, we should
> wait for one or both of the extension specifications meet the CR exit
> criteria. This is why I've resolved this as LATER, instead of moving the
> bug into the HTML.next component (as we've been doing with other feature
> requests).
I think this is the right approach.
I don't want the Responsive Images CG (RICG) to replicate work; And I think
Hixie is in a much better position to specify the normative text needed to meet
the use cases that the RiCG is pursuing. The RICG is focusing on the use cases
to see if img@srcset meets all of them.
The RIGC are working from the hypothesis that img@srcset does meet the use
cases, but have identified a few places where it may not (Work in Progress):
https://github.com/Wilto/draft-prop/blob/master/UseCaseComparisons.md
We've also moved work to github:
https://github.com/Wilto/draft-prop/
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 3 October 2012 10:38:53 UTC