- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Fri, 25 Apr 2014 12:36:55 -0700
- To: Rick Byers <rbyers@chromium.org>
- Cc: François REMY <francois.remy.dev@outlook.com>, Oren Freiberg <oren.freiberg@microsoft.com>, CSS WG <www-style@w3.org>
On Fri, Apr 25, 2014 at 12:32 PM, Rick Byers <rbyers@chromium.org> wrote: > On Thu, Apr 24, 2014 at 9:20 PM, Oren Freiberg <oren.freiberg@microsoft.com> > wrote: >> It seems Rick felt we should match both but it looks like Chrome never >> implemented it. Rick do you still feel the same way and plan on implementing >> a solution that supports matching both fine and coarse on a hybrid device? >> >> http://lists.w3.org/Archives/Public/www-style/2013Apr/0534.html > > I'd like to yes, but I didn't want to change anything here (or even finish > our implementation of this feature) until this was reflected in the spec > (indicating there was some kind of consensus here). My understanding from > my last discussion with Tab was that he planned to update the spec to > explicitly state that setting BOTH coarse and fine was OK when multiple > input devices are considered 'primary'. That was done some time ago, btw. ^_^ > In general I haven't heard much interested from other vendors on these MQ > features, so I've been hesitant to commit ourselves beyond the minimal > pointer:coarse support we added. If IE was interested in these, I'm sure we > could quickly come to an agreement on behavior that we'd both implement :-) And if y'all agree on something more specific than what the spec currently suggests, please let me know so I can spec it.
Received on Friday, 25 April 2014 19:37:42 UTC