6 ms·
"HTML 5" features like <input type="text" x-webkit-speech> surely won't work.
by sheffield 15y ago
"HTML 5" features like
<input type="text" x-webkit-speech>
surely won't work.
- speckledjim 15y agoMost will fail gracefully though. For example that one will just render as a normal text input on older browsers.
- est 15y agoMicrosoft had their Windows SpeechAPI available in IE, like what, 5.0? var a = new ActiveXObject("SAPI.SpVoice"); It can do TTS and Voice Recognition, locally And don't forget MIDI and Drect3D support was introduced in IE4. Before SVG, there was a trend of VRML in the industry and VML was added to IE. And don't forget, the very first AJAX as made possible by the IE xmlhttp object. TIME+dHTML was cool before Flash, even before these Web2.0 and HTML5 cool kids start yammering around. And then Microsoft killed these features with their Silverlight.
- sheffield 15y agoThe emphasis was in webkit.
- sp332 15y agoFeatures that haven't been standardized are put in their own namespaces. For example, webkit-* and mozilla-* had conflicting implementations of CSS gradients for a while. After the standard was ratified, the prefix was removed. Safari still supported the old webkit-* syntax, and Firefox still didn't, just like before, but new pages could use the functionality without the prefix and it would work in both browsers. Also, if webkit has settings or features that are specific to the library used, it makes sense to put those in a different namespace as well, to avoid pollution.
- yuhong 15y ago>IE xmlhttp MSXML XMLHTTP. MSXML 2.0 released with IE5 was first to support it. It got copied first by Mozilla, BTW, then as AJAX caught on in 2004 Safari copied it too.
- ch0wn 15y agoWhat is wrong with that? It's a vendor extension, like most new CSS and JS features are implemented. A draft specification for the Speech API exists since last October, if I'm not mistaken. So why would that not work?