3 ms·
The bad tablet experience on Windows is entirely the fault of app developers, Chrome included. Chrome's HiDPI and touch support on non-mobile are an atrocity an
by kevingadd 8y ago
The bad tablet experience on Windows is entirely the fault of app developers, Chrome included. Chrome's HiDPI and touch support on non-mobile are an atrocity and it's entirely their fault. They've gotten a little better lately, at least...
In comparison if I use (classic) edge to browse and read on my tablet, it's totally fine. Firefox is relatively okay as well (similar issues though, because it just doesn't get much testing).
Having two monitors of different DPIs makes it especially obvious how bad most apps are at DPI. The good ones stand out to a dramatic extent. DPI is a difficult thing to implement, but Win9x has had tooling and support for it since Windows 10 and they improve it with every release. When I implement support in my apps it really doesn't take that much effort, just forethought.
For one example: Chrome's scrollbars and other widgets are utterly atrocious on touch (even on Android it's kind of bad). The standard Win32 scrollbars and other widgets can have all their sizes manually adjusted in the registry, and by default many of them will automatically adjust when you're in touch mode. I was easily able to make scrollbars bigger across literally everything except Chrome.
- wslh 8y ago> The bad tablet experience on Windows is entirely the fault of app developers I don't think so. Microsoft should make easier to develop for tablet mode if they want adoption, the DPI issues happen also in Microsoft applications! The Win32 APIs are a legacy mess and Microsoft has a long tradition in delivering lot of frameworks which ends in failure (WPF, Silverlight, etc). BTW, Google Docs copy & paste in tablet mode doesn't work in Firefox either.