Introducing the Chromium HTML5 discussion group
Ernest Delgado
HTML5 has introduced a new set of features that modern browsers
support to help web developers create richer web applications. We
realize that, as with anything new, there will always be questions and
a learning-curve involved in adopting these new APIs. This is the
group to help with questions about how to use these new APIs from
HTML5 (and other standards groups) that are now available for use
within Chromium and Google Chrome, the extensions framework and Google
Chrome OS.
If you also want to find out more about Google Chrome's implementation
of HTML5, ask questions about developing apps on Google Chrome, or
announce events and samples you're working on, you've come to the
right place. However, in order to keep the discussion manageable, if
you have questions about developing extensions, please go to:
http://groups.google.com/a/chromium.org/group/chromium-extensions
if you are looking for information about contributing to Chromium open
source projects,
please go to:
http://dev.chromium.org/developers/discussion-groups
We're excited to continue to provide more capabilities in each Google
Chrome release, and even more excited to see all of the amazing
innovations that developers will bring to users with the help of these
new capabilities.
Ernest
Raju Bitter
features. Due to the fact that Google can provide the browser, the
JavaScript and rendering engine, the applications and the OS you are
in a position to innovate web applications without having to be afraid
of leaving user of old IE versions outside (they could even use Chrome
Frame). What impact do you think will this "proof-of-concept" in
production for HTML5 have on the evolution of the standards, maybe
even new concepts and ideas which might go back into the
standardization process?
With the strong position of Microsoft and IE in the past it was very
difficult to adopt any of the innovative JavaScript features in
applications when targeting a large percentage of users. It's a
relieve to see that modern browser like Chrome or Webkit enable
developers to make use of HTML5 - which especially is interesting for
mobile apps. What role do you see for proprietary technologies like
Flash in the future? It's still difficult to access the microphone and
webcam out of webapps without using Flash, especially when you are not
only targetting one browse and OS. What are your visions for HTML5 or
open standards based webcam and microphone access? Maybe even a SIP
phone client inside Chrome/Chromium?
Alex Russell
> I really like the fact that Google is so quick at adopting HTML5
> features. Due to the fact that Google can provide the browser, the
> JavaScript and rendering engine, the applications and the OS you are
> in a position to innovate web applications without having to be afraid
> of leaving user of old IE versions outside (they could even use Chrome
> Frame). What impact do you think will this "proof-of-concept" in
> production for HTML5 have on the evolution of the standards, maybe
> even new concepts and ideas which might go back into the
> standardization process?
>
> With the strong position of Microsoft and IE in the past it was very
> difficult to adopt any of the innovative JavaScript features in
> applications when targeting a large percentage of users. It's a
> relieve to see that modern browser like Chrome or Webkit enable
> developers to make use of HTML5 - which especially is interesting for
> mobile apps. What role do you see for proprietary technologies like
> Flash in the future?
Plugins continue to provide an important way for developers to access
native capabilities that browsers haven't provided access to yet or
for which support is uneven.
> It's still difficult to access the microphone and
> webcam out of webapps without using Flash, especially when you are not
> only targetting one browse and OS. What are your visions for HTML5 or
> open standards based webcam and microphone access? Maybe even a SIP
> phone client inside Chrome/Chromium?
It seems natural that there should be <input type="video"> and <input
type="audio"> elements that would provide ways for web applications to
capture user-provided a/v content. There are a lot of hard questions
to answer before that's as easy to use as it is to type, though.
Regards
Mike Taylor
> [snip]
>
>> It's still difficult to access the microphone and
>> webcam out of webapps without using Flash, especially when you are not
>> only targetting one browse and OS. What are your visions for HTML5 or
>> open standards based webcam and microphone access? Maybe even a SIP
>> phone client inside Chrome/Chromium?
>>
> It seems natural that there should be<input type="video"> and<input
> type="audio"> elements that would provide ways for web applications to
> capture user-provided a/v content. There are a lot of hard questions
> to answer before that's as easy to use as it is to type, though.
>
> Regards
>
webcams as one possible use case. Mind you, this is merely months old.
http://lists.whatwg.org/pipermail/commit-watchers-whatwg.org/2009/003599.html
http://www.whatwg.org/specs/web-apps/current-work/#devices
Best,
Mike
Ernest Delgado
That part of the spec is indeed a very recent experimental idea.
I am looking forward to seeing who'll be the first browser to play
with it.
On Jan 26, 5:38 pm, Mike Taylor <miketa...@gmail.com> wrote:
> On 1/26/10 6:29 PM, Alex Russell wrote:> [snip]
>
> >> It's still difficult to access the microphone and
> >> webcam out of webapps without using Flash, especially when you are not
> >> only targetting one browse and OS. What are your visions for HTML5 or
> >> open standards based webcam and microphone access? Maybe even a SIP
> >> phone client inside Chrome/Chromium?
>
> > It seems natural that there should be<input type="video"> and<input
> > type="audio"> elements that would provide ways for web applications to
> > capture user-provided a/v content. There are a lot of hard questions
> > to answer before that's as easy to use as it is to type, though.
>
> > Regards
>
> Hixie has done a little work on speccing a <device> element, with
> webcams as one possible use case. Mind you, this is merely months old.
>
harsh9t
On Feb 1, 1:08 am, Ernest Delgado <erne...@google.com> wrote:
> Hi Mike,
> That part of the spec is indeed a very recent experimental idea.
> I am looking forward to seeing who'll be the first browser to play
> with it.
>
> On Jan 26, 5:38 pm, Mike Taylor <miketa...@gmail.com> wrote:
>
>
>
> > On 1/26/10 6:29 PM, Alex Russell wrote:> [snip]
>
> > >> It's still difficult to access the microphone and
> > >> webcam out of webapps without using Flash, especially when you are not
> > >> only targetting one browse and OS. What are your visions for HTML5 or
> > >> open standards based webcam and microphone access? Maybe even a SIP
> > >> phone client inside Chrome/Chromium?
>
> > > It seems natural that there should be<input type="video"> and<input
> > > type="audio"> elements that would provide ways for web applications to
> > > capture user-provided a/v content. There are a lot of hard questions
> > > to answer before that's as easy to use as it is to type, though.
>
> > > Regards
>
> > Hixie has done a little work on speccing a <device> element, with
> > webcams as one possible use case. Mind you, this is merely months old.
>
> >http://lists.whatwg.org/pipermail/commit-watchers-whatwg.org/2009/003...
>