- From: Sunyang (Eric) <eric.sun@huawei.com>
- Date: Tue, 26 Jun 2012 07:38:54 +0000
- To: Mathew Marquis <mat@matmarquis.com>, Maciej Stachowiak <mjs@apple.com>
- CC: "Edward O'Connor" <eoconnor@apple.com>, HTML WG <public-html@w3.org>
+1, expecting HTML.NEXT to kickoff. And I think we can do it in HTML.NEXT, if during process we find it very popular, we can try to bring a bug back to HTML5. -----邮件原件----- 发件人: Mathew Marquis [mailto:mat@matmarquis.com] 发送时间: 2012年6月26日 5:29 收件人: Maciej Stachowiak 抄送: Edward O'Connor; HTML WG 主题: Re: Proposed adaptive image element On Jun 25, 2012, at 5:14 PM, Maciej Stachowiak wrote: >> I’ll definitely defer to you guys on matters of process, as I’m well outside of my wheelhouse there. My only concern is the effect this decision could have on the time between introduction and a potential native implementation, if any. If this should be put off until HTML.next, what impact would that likely have? >> >> This is a rapidly growing problem, and has been for some time. I worry about putting off the potential for a native solution, as developers find increasingly “creative” ways to work around the issue — or, perhaps worse still, simply opt to serve images that account for the “highest common denominator” at an additional bandwidth cost to users who may see no benefit. > > Sometimes, vendors are willing to implement features based on only a draft future spec or a rough proposal. So deferring a feature to HTML.next does not necessarily block implementation work. > > In addition, HTML.next work will be starting fairly soon, without waiting for HTML5 to be finished. So waiting for HTML.next does not have to be a significant delay. Excellent! In that case: no complaints here! > > Without commenting on the merits of this particular case, I agree with Ted's comments that in general, we should hold off on adding HTML5 features. > > Regards, > Maciej >
Received on Tuesday, 26 June 2012 07:44:41 UTC