Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #7158 > unrolled thread

Re: know its ipad

Back to article view | Back to comp.lang.javascript

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  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

#7158 — Re: know its ipad

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/93e05bc723164080/17d5759265e496fe?lnk=gst&q=detect+touch+support#17d5759265e496fe
> 
> 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.

See the My Library attachTouchListeners add-on. It's a simple example of handling mouse and (single) touch events with a single API.

Only time it's needed is for drag and drop interfaces (a relative rarity on the Web).

[toc] | [next] | [standalone]

#7164

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.
--
Garrett

[toc] | [prev] | [next] | [standalone]

#7165

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.

Andrew Poulos

[toc] | [prev] | [next] | [standalone]

#7190

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.

[toc] | [prev] | [next] | [standalone]

#7189

On Oct 10, 1:39 am, dhtml <dhtmlkitc...@gmail.com> 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).

You made that mistake, period. I did not. See the example I cited.

> There may be one or more
> input devices such as mouse, keyboard, or some yet-to-be-invented
> input device.

No kidding. :)

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.javascript

csiph-web