10 ms·
When IE gave us beautiful, fast touch interactions, and nobody cared
- zawaideh 12y agoI wish we had PointerEvents as well!
- liotier 12y agoAnd NullPointerException while we're at it - if we're going to mix random stuff in CSS properties, why not go all the way ?
- deleted 12y ago[deleted]
- msoad 12y agoI've worked with -ms-scroll-snap-points. It's very limited and an anti-pattern for separation of concerns. You're putting logic of how scrolling should behave in CSS. It's becoming very difficult to do more than just simple logic with this. I've tried updating -ms-scroll-snap-points property on the fly but it didn't work that well. We need better scroll APIs for sure, but in DOM JavaScript API not in CSS
- taeric 12y agoI'm curious on why logic of how scrolling should behave should not be in CSS. If the concerns are DOM = Data and CSS = presentation. JS would be Dynamic on either of those. That is, if you can statically state your scroll points, it would seem that CSS would make sense for that.
- WorldWideWayne 12y agoIt's nothing new. Scrolling behavior logic has been in CSS since forever with all of the different overflow properties.
- pcwalton 12y ago> We need better scroll APIs for sure, but in DOM JavaScript API not in CSS If it's in CSS, the browser can fundamentally optimize it better. DOM APIs have to run on the JS thread ("main thread") and contend with GC pauses, image decoding (in some browsers), layout (in all mainstream browsers), painting (in most browsers) and so forth. However, if it's in CSS, it can be proxied out to the compositor thread, which runs very little. This makes a huge difference in responsiveness.
- bshimmin 12y agoJust as the article says, I'd never heard of this. Looking at the example, the CSS seems rather unwieldy: -ms-scroll-chaining: chained; -ms-overflow-style: none; -ms-content-zooming: zoom; -ms-scroll-rails: none; -ms-content-zoom-limit-min: 100%; -ms-content-zoom-limit-max: 500%; -ms-scroll-snap-type: proximity; -ms-scroll-snap-points-x: snapList(100%, 200%, 300%, 400%, 500%); -ms-overflow-style: none; I don't really know if any of that stuff actually belongs in CSS as the majority of people see it (and `snapList` certainly doesn't feel like CSS to me).
- werdnapk 12y agoThis is hardly the worst of what some of the new "standard" CSS3 properties looks like. Those MS properties actually look sane in comparison to recent CSS3 properties.
- putzdown 12y agoA pet peeve: The author sets his story "many years ago at Zynga." "Many years ago" speaks to me of long years past; like, decades—surely at least a decade. But Zynga was founded relatively recently, in 2007. Why do people in the tech industry tend to talk about what is really a few years ago as if it were ancient eons past? Is the author simply so young that < 8 years seems like "many years" to him?
- badloginagain 12y agoGiven how fast things tend to move in the industry, and how a person can be doing very different things now than they were a few short years ago, I think one can forgive the author for perceiving the peak Zynga years as longer than it actually may be. It's remarkable to look at where I was 8 years ago compared to now, regardless of age really.
- callum85 12y agoIt's just you. Most people would agree 6-7 years counts as "many" in this industry.
- cgriswald 12y agoIt's not just him. "Many" means "a large number" not "it feels like it has been awhile because of the pace of change." Zynga has not been around "many" years, by definition. Even worse, that project was actually completed some time in 2011. I think we can agree that 3-4 years is not "many". But the worst part of that sentence is the change in tense. ;)
- polarix 12y agoThis might have to do with the accelerating human perception of time. Can't 5 years really feel like eons? If the author were 25, that would be a significant chunk of life, and I'm hoping you're not intending to imply that all 25 year olds should be dismissed out of hand. But it's interesting -- people who have worked in tech during M$FT's heyday probably do want to dismiss this argument without consideration. Is the real story here that peoples' unconscious attitudinal memory is long enough that some companies' prior actions can never be forgiven?
- avolcano 12y agoIt'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 :)
- serve_yay 12y agoThe phrase "once bitten, twice shy" comes to mind, except instead of "once", more like "a million bazillion times".
- guelo 12y agoYou mean like how entire industries were created after being bitten by IE's XMLHttpRequest?
- idbehold 12y agoNo, that only happened once. He's talking about the "million bazillion times" they ignored standards in favor of proprietary APIs which resulted in much pain and suffering for both developers and consumers alike.
- serve_yay 12y agoNo?
- smacktoward 12y agoWhich Microsoft, in classic Microsoft fashion, completely failed to recognize the significance of. XMLHttpRequest was used only by Outlook Web Access (the kludgey old MS Exchange webmail client), and never took off until Google saw the potential in it and used it in Google Maps.
- anocendi 12y agoTo be fair, IE gave us non-beautiful, non-fast interactions for .... how long?
- glesica 12y agoI think the reason nobody seems to care about IE today isn't that it is a terrible browser, as in the past, but that it doesn't run on Mac OS or GNU/Linux. There are certainly people doing development on Windows, but more (at least of people who would use features like this) doing so on other platforms. Until IE is cross-platform, many developers will continue to ignore it because they have no reasonable way of using it and getting to know it.
- adventured 12y agoDo you have stats to back up the premise that more developers (or those that would use features like this) are on non-Windows platforms? Windows still has roughly 90% of the total desktop + laptop market. I find it hard to believe it doesn't still have a majority of such developers. GNU/Linux is ~2% of the market.
- fractalb 12y agoI don't think 90% percent people are using IE
- adventured 12y agoNobody was implying it does. The parent referred to Windows, Mac, GNU/Linux and developers using those platforms, with the premise being that IE needs to be cross-platform because so many more developers are using non-Windows platforms.
- iherbig 12y agoWhich was not at all what adventured was saying. They were responding to glesica's assertion that the reason nobody cares about IE is that it isn't cross-platform. To counter this assertion, adventured said that 90% of the desktop/laptop market uses Windows, so it seems unreasonable that the majority of people would not have access to IE as a reason for not using it. Adventured was not suggesting that 90% of people are using IE; they were suggesting the exact opposite and asking why that is, because glesica's reasoning seems intuitively flawed.
- 12y ago
- jpetersonmn 12y agoIt's kind of ironic that this article praises IE, yet the article itself doesn't display properly in IE. The main article content is covered by the current projects. Works fine in Chrome though.
- atmosx 12y agoExactly my thoughts, so you don't have to look hard in order to understand why nobody cares. Not even the author really cares.
- paulbakaus 12y agoOP here. Thanks for the bug report! I'll fix. It's true, haven't used IE in the while, but that wasn't the point of the article. I care deeply about the web as a whole, and all of its evolution.
- paulbakaus 12y ago...aaand it's fixed. Was a stupid recent spelling mistake.
- junglecode 12y agoFirefox is shipping the standardized features without prefixes: https://bugzilla.mozilla.org/show_bug.cgi?id=945584 https://bugzilla.mozilla.org/show_bug.cgi?id=945584
- michaelbuddy 12y agothe windows browser on MS Surface Pro is also good, fast responsive, and the only one with that quality of behavior on a touch device.
- fuzzywalrus 12y agoI wouldn't go quite that far, MS touch has been hell with some pseudo states as hovers often require holding a finger down as it treats a mouse hover and touch hover the same in IE10. Its unexpected when Android and iOS both freeze on the hover state.
- gtk40 12y agoI use IE11 almost exclusively these days when I'm on Windows, and this part of why. But ironically, this article doesn't even work on it. (and zooming doesn't fix the issue) http://i.imgur.com/jlNT8vt.png http://i.imgur.com/jlNT8vt.png
- paulbakaus 12y agoThanks for letting me know! Will fix.
- WalterBright 12y agoIronically, that web page doesn't render properly in IE. (The right side of the article text is overlaid by the "Current Projects" sidebar.)
- bhauer 12y agoAmusing. It does, however, kick over to a proper layout when the width is narrower. I had originally read this article on my Windows Phone and it rendered just fine. It also renders fine in desktop IE if you make the window narrow.
- otakucode 12y agoIt's almost like the web was never designed as an application platform and it's performing like a document presentation system with applications shoehorned into it.
- otakucode 12y agoDon't just downvote because you like the web as an application platform. I am serious. The exact reason that these specific extensions being discussed are not standard now, along with dozens of others that would make application development much easier, is because providing an application platform is explicitly not the goal of HTML, CSS, or the web in general.
- striking 12y agoI do think that interactive documents are a very useful tool and that HTML and CSS get us there; but I totally agree that HTML and CSS do not make good applications. The web is for documents. Now if only there were a way to make applications that were delivered in the same fashion as documents, but not constrained by the same poor decisions.
- 72deluxe 12y agoThis is incredibly perceptive and true. It is odd to see how many people are trying to make the web do odd things like running applications in browsers. The constant testing that put people off writing cross-platform applications all those years ago is now multiplied significantly with all the testing they need to do on different browsers under different OSes, or even the same browsers but different versions on the same OSes. It's daft.
- mathgeek 12y agoPart of the problem that IE has had for a long time, and that the CSS this article discusses is a continuation of, is that IE sits in its own world as far as CSS standards go. It sure sounds like the great tool for carousels that this article discusses is still IE-specific. That means you can't use it on any other browser, which effectively means it's DOA from the get go.
- untog 12y agoYet both Apple and Google do this, frequently, and fewer people complain.
- reitanqild 12y agoIt might be annoying that this happens today but bear in mind that MS brought this onto itself by ignoring everyone but Windows users for year after year. Our way or the highway. Now that they have finally repented they will still need to reap what they have sown. At least that seems to be a valid principle elsewhere. :-) (Note that I say this as someone who is currently very close to be a fanboy of "new Microsoft")
- malkia 12y agoI know it's on the web, and has to work on tons of browsers, thousands of devices, but "15-20fps" have never been acceptable figure in console game development. Hell even 30fps is not acceptable for some games (fighting, racing, first person shooters). So having 60fps in the browser is incredible!
- differentView 12y agoIt's as if reputation matters.