Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.javascript > #7190
| From | David Mark <dmark.cinsoft@gmail.com> |
|---|---|
| Newsgroups | comp.lang.javascript |
| Subject | Re: know its ipad |
| Date | 2011-10-10 21:40 -0700 |
| Organization | http://groups.google.com |
| Message-ID | <0f78583e-e322-4841-bfb5-b94d457f2975@j31g2000vbl.googlegroups.com> (permalink) |
| References | (8 earlier) <4f034459-6218-4cd1-8125-1b9b70da4b2c@j9g2000prj.googlegroups.com> <fuudnQFKubzq1YDTnZ2dnUVZ_hSdnZ2d@westnet.com.au> <20892229.2514.1318210553787.JavaMail.geo-discussion-forums@yqcs10> <d1292fb4-6395-4b19-85fe-15c9d5fc815c@k24g2000prl.googlegroups.com> <BP-dnbw-_MZfDg_TnZ2dnUVZ_iydnZ2d@westnet.com.au> |
On Oct 10, 2:42 am, Andrew Poulos <ap_p...@hotmail.com> wrote: > On 10/10/2011 4:39 PM, dhtml wrote: > > > > > > > > > > > On Oct 9, 6:35 pm, David Mark<dmark.cins...@gmail.com> wrote: > >> On Wednesday, July 13, 2011 3:25:31 AM UTC-4, Andrew Poulos wrote: > >>> On 13/07/2011 4:31 PM, RobG wrote: > >>>> On Jul 13, 4:29 pm, RobG<rg...@iinet.net.au> wrote: > >>>> [...] > >>>>> You should be testing for touch support, not what the device is. > > >>>> Because I know you're going to ask: > > >>>> Detecting support for event types > >>>> <URL: > >>>>http://groups.google.com/group/comp.lang.javascript/browse_frm/thread... > > >>> So a browser that supports touch events won't claim to support touch > >>> events when the browser is on a device that can't send touch events. Is > >>> that true? > > >> No. Chrome on the desktop "supports" touch events, regardless of the hardware. > > > The reason for this: > > groups.google.com/group/comp.lang.javascript/browse_thread/thread/ > > e7a70a39b22839de/27d60472800eb97a#27d60472800eb97a > > > Regardless, it is still fallacy to claim that touch events being > > present means that there the user will interact using a touch > > interface (and I made that mistake, too). There may be one or more > > input devices such as mouse, keyboard, or some yet-to-be-invented > > input device. > > To me it makes sense that if a device cannot support touch events it > does not present them. It's the browser that presents those features. They may or may not remove them for hardware that lacks touch capabilities. Perhaps they don't want to make assumptions as a new input device could be connected at any time.
Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: know its ipad David Mark <dmark.cinsoft@gmail.com> - 2011-10-09 18:35 -0700
Re: know its ipad dhtml <dhtmlkitchen@gmail.com> - 2011-10-09 22:39 -0700
Re: know its ipad Andrew Poulos <ap_prog@hotmail.com> - 2011-10-10 17:42 +1100
Re: know its ipad David Mark <dmark.cinsoft@gmail.com> - 2011-10-10 21:40 -0700
Re: know its ipad David Mark <dmark.cinsoft@gmail.com> - 2011-10-10 21:38 -0700
csiph-web