3 ms·
That 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
by josho 12y ago
That 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 :)