#CSS3-UI editor's WD: added box-sizing:padding-box, ime-mode, text-overflow:string. http://j.mp/css3uie longurl: http://dev.w3.org/csswg/css3-ui/
IE10 drops Conditional Comments, XML Data Islands http://j.mp/ie10cc. Now please add HTML5 History API! longURL: http://blogs.msdn.com/b/ie/archive/2011/07/06/html5-parsing-in-ie10.aspx
says @BenWard: "buttons as 'tweet actions'". Good, proper subset of "web actions". "intent"=pop-up is confusing: webintents.com predates Twitter's use of the phrase "web intents" and uses it to mean everything: registry and discovery of APIs, and supposedly "a system that allows the user to control the services that their applications interact with". Sadly though a mention of "user" without any mention or diagrams of user-interaction, user-flow etc. It's an example of what I was complaining about: tantek.com/2011/187/t1/technical-folks-protocols-without-user-scenarios-ux. See also "Web Introducer" draft spec: web-send.org/introducer which appears to also define a web "intent". Regardless, love the Twitter Web Intents feature and design dev.twitter.com/pages/intents (nice screenshots, action URLs, pop-up design and flow etc.), just dislike the "web intents" term. in-reply-to: twitter.com/BenWard/status/89009190588268545
not considered? http://instagr.am/p/HJiIw I'm going to try using "web actions" instead of "web intents". search: 
from: https://encrypted.google.com/search?q=%22web+actions%22+%22web+intents%22 Wonder how long it will take this post to show up in that search.
problem with the term "web intents" is that they're not *intents*, they're *actions* that users take across the *web*.
we've done this already. documents over files, apps over programs. using user-centric terms leads to better usability.
says @benward "'Web Intents' term isn't for users" As user-centric devs can we at least try to use user-centric terms?
t