3 ms·
It's worth pointing out that Microsoft primarily invented this for HTML5 Windows 8 apps (along with some interesting, if incredibly underbaked, JavaScript view
by avolcano 12y ago
It's worth pointing out that Microsoft primarily invented this for HTML5 Windows 8 apps (along with some interesting, if incredibly underbaked, JavaScript view libraries to go along with it). That is why the APIs here might seem like way-too-high-level abstractions - they were trying to encapsulate the UX features Windows 8 had, like scroll snapping within item grids.
It was nice, and necessary, to use there because it made it relatively easy to make HTML5 apps that looked and felt like a native counterpart on the same platform. I don't know if they would have fit in on the general web, but it was cool to see them take a crack at nicer touch scrolling in CSS.
- josho 12y agoThat certainly explains why the standardization process went nowhere. Ie. It was a UI feature largely specific to a single platform's native UI paradigm, and at that a platform with a minor marketshare. Regardless, this is a great example of how innovation should happen. That is browser vendors try out new things, and those experiments that succeed become standardized. In this case it sounds like this experiment is a step forward, but not quite reusable enough to support standardization across platforms.
- paulbakaus 12y agoOP here. I actually agree, and that seems to be Google#s stance right now, from what I've heard (I work for Google but wasn't involved in the technical work on this feature so far). We might need an API that is slightly more low level but achieves the same. My point was that we need this functionality, and no other API offers it, so I took anything I could get :)