User Experience on Discourse with optional touch-input

Continuing the discussion from here, here, here, and here

All the topics linked above have in common that there are issues with Discourse, generally related to UX, when a using Discourse on a system that has touch, but primarily is interacted with via keyboard and mouse. First, it is my understanding (according to @codinghorror) that it is not possible with JS and HTML to detect this type of system, separately from any other system that has a touch input.

With that out of the way, I would like to suggest that this issue as a whole needs to be looked at seeing how the PC market is moving in recent years. When Discourse was first started, you could generally see two types of devices: mobile - like iPads, iPhones, Android phones/tablets, etc. - and desktop, like laptops, workstations, full-size PCs, etc. Today, the device landscape is very different. Thanks in part to a much better adoption of Windows 10 vs Windows 8, more “desktop” devices are coming with touch as an option. Now, touch is an option on most devices purchased from major manufacturers, even in their “business” models, and devices like Microsoft’s Surface, Lenovo’s Yoga, and similar 2-1/convertible designs are becoming much more popular in the marketplace.

Given that there is no reliable way to detect these devices, whether the user has a mouse and keyboard attached, or reliably guess what type of UX the user prefers, I would like to suggest a user setting “toggle” for Discourse. The closest analogous feature I can think of is Windows 10’s Tablet mode, that is user toggleable and makes changes to the UI to make Windows more (or less) friendly to touch. I understand that might not be ideal, as currently Discourse has a fully responsive design, and has purposefully avoided distinguishing “mobile mode” from “desktop mode”, but for users who use a laptop with an attached touch-enabled monitor, or multiple laptops some with and some without touch, it is jarring to have Discourse react differently depending on if the external monitor is connected, or if the device has touch or not.

4 个赞

We have some precedent now, for iPads we have a “I have a keyboard” user setting

9 个赞

So I haven’t used a device with touch (other than a phone) in 2+ years. Will see if I can get my hands on a Windows laptop with a touch screen to see the current situation.

5 个赞

I actually have one, will try it out on Monday

4 个赞

Didn’t @sam add this for iPad specifically? It could be opened up to everyone at the risk of confusing people.

看来这件事没发生?

那像 Surface Pro 这样带有可拆卸键盘的设备呢?

我想建议增加一个“我有鼠标/触控板”的用户设置,其功能与“我有键盘”的用户设置类似。

确实发生了,我做了一系列修改,我们需要一个额外的用户设置,即“我有键盘”。

之前运行得非常顺利。

打算再测试一次,以确认一切仍然正常。

3 个赞

我又有了可选的触控设备(带触摸屏的笔记本电脑)。一直半定期使用,没发现什么大问题。Justin_Vega,有什么特别不符合预期的功能吗?

1 个赞

我们有 3 个问题,@pmusaraj 将在 iPad + 键盘环境下进行调查:

  1. 覆盖层遮挡了蓝色回复按钮的显示
  2. 回复的键盘快捷键无法将焦点聚焦到编辑器
  3. Tab+Enter 无法提交
9 个赞

提醒一下,新款带键盘/触控板的 iPad 设备要到5 月才发布。那大约是两个月后。我之所以知道,是因为我试着订购了一台。

6 个赞

在我在首帖中链接的所有主题中,只有这一个似乎仍然是个问题:

在非触控设备上,URL 是一个文本字段,默认高亮以便复制。在触控设备(如我的笔记本电脑)上,它是一个超链接,并不总是被高亮。我将利用一个“我有键盘”(最终文案待定)的设备特定用户偏好设置。

3 个赞

我们应该尝试在不依赖用户偏好设置的情况下修复共享问题。

5 个赞

完全赞同 :clap: 我非常高兴你移除了该设置,因为添加一个几乎没人会发现的特殊“魔法”设置几乎没有价值。

5 个赞

需要保持此话题开放,我们仍在追踪 User Experience on Discourse with optional touch-input - #13 by pmusaraj

1 个赞

我在 iOS 触控设备上无法让链接正常显示,它直接跳到了系统的分享对话框。Joshua,你用的是 Windows 触控设备吗?比如带触摸屏的笔记本电脑?

1 个赞

正确,适用于带触摸屏的 Windows 10 笔记本电脑。Android 和 iOS 会打开系统共享对话框。

1 个赞

我不认为这个问题可以解决,@jomaxro,所以我不明白你为什么要重新打开它……正如 Sam 所说:

因此,唯一可能的解决方案——添加一个设置——已经被否决。还有什么可讨论的呢?

我自己对此持开放态度,但我倾向于同意:如果我们提供这个设置,只有 0.00000001% 的用户会发现或使用它。

来自

我原本以为会尝试在不使用站点设置的情况下修复这个问题…

1 个赞