Hi James,
1. I'm thinking about the possibility of a UA to offload the speech
recognition
task to an external local service or application, such as an input method or
a text service or even a browser extension. I'm just wondering if the user
interaction flow would still be same when it
Am 19.06.2010 21:07 schrieb Garrett Smith:
What is the correct expectation for the outcome of submitting a SELECT
that has a disabled, selected OPTION?
I can't answer this exact question, but to go back to the original
question: Maybe this is the point where the @required attribute makes
Hi all,
I wonder why a element should have .text which
is basically just the same thing as
.textContent.
I'd prefer removing .text.
-Olli
On Mon, Jun 21, 2010 at 11:09 AM, Olli Pettay olli.pet...@helsinki.fi wrote:
Hi all,
I wonder why a element should have .text which
is basically just the same thing as
.textContent.
I'd prefer removing .text.
It's actually worse, see
On 6/21/10 9:25 PM, Jonas Sicking wrote:
On Mon, Jun 21, 2010 at 11:09 AM, Olli Pettayolli.pet...@helsinki.fi wrote:
Hi all,
I wonder why a element should have .text which
is basically just the same thing as
.textContent.
I'd prefer removing .text.
It's actually worse, see
On Mon, Jun 21, 2010 at 12:00 PM, Olli Pettay olli.pet...@helsinki.fi wrote:
On 6/21/10 9:25 PM, Jonas Sicking wrote:
On Mon, Jun 21, 2010 at 11:09 AM, Olli Pettayolli.pet...@helsinki.fi
wrote:
Hi all,
I wonder why a element should have .text which
is basically just the same thing as
It's important to realize that Flash fullscreen is about a lot more than
just having the video play. For many sites (such as us at YouTube), the
controls/UI are part of the fullscreen experience. Unless you can fullscreen
a canvas or somehow allow controls and other elements (subtitles,
On Tue, Jun 22, 2010 at 11:22 AM, Kevin Carle kca...@google.com wrote:
It's important to realize that Flash fullscreen is about a lot more than
just having the video play. For many sites (such as us at YouTube), the
controls/UI are part of the fullscreen experience. Unless you can fullscreen
Having immensely enjoyed using w3.org standard XML/XSL
transforms in my web projects , I would really like
the HTML5 spec to consider the addition of two
element level attributes (XML and XSL)
These two attributes would at a minimum take
URLs to the respective .xml and .xsl sources.
Use cases
