Touch++, again. Same points I said in September. Gerv, do you have an online place that captures the discussion? The reason I ask this is my interest to really understand what is the current assumption nowadays on what UA stands for and the complexities involved in this discussion. Plus I wanted to understand a table about reasoning from other vendors.
m On Mon, Nov 12, 2012 at 2:36 PM, <jim.math...@gmail.com> wrote: > I don’t see how this information will be of any use in deciding how to > present content, and will likely be used in the wrong way which will break > user experiences. > > We have a related situation with W3C touch event interfaces. Web authors > are using their presence as a way to detect mobile devices with the > assumption that these devices don’t support mouse input. See bug 806805 for > feel for what breaks when we add support (rightfully) for touch input > events in the desktop product. I think it’s possible “Tablet” or “Touch” in > the UA could be abused in the same way. > > The real problem here seems to be a lack of a good way to detect device > capabilities, which can change in real-time while the browser is running. > For example, I have a Samsung Series 7 that has touch, a dock, a mouse, and > a keyboard. Docking the device makes it a desktop, undocking it makes it a > tablet. I’d like web sites to react appropriately to these changes – IMHO > this is something that should be solved via information exposed to content > through js or css, and through better documentation / examples on MDN. > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > -- www.telasocial.com _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
