[whatwg] Device Element

Silvia Pfeiffer silviapfeiffer1 at gmail.com
Tue Dec 28 00:53:51 PST 2010

How about making a  concrete proposal as to what it should look like?
If Google was to implement it and turn it into a concrete proposal, I
wouldn't have a problem with it either. As it is right now the spec
for usb/RS232 is useless IMHO.


On Tue, Dec 28, 2010 at 4:02 AM, Diego Perini <diego.perini at gmail.com> wrote:
> On Tue, Dec 28, 2010 at 3:16 AM, Seth Brown <learc83 at gmail.com> wrote:
>> I saw on the spec page that you were considering limiting the device
>> element to audio/visual streams. I thinks this would be a mistake.
>> I'm currently working on integrating serial port connected hardware
>> with a web application I'm developing. The only solution is for the
>> user to install local adapter software. This defeats the purpose of
>> using a web app over desktop software.
>> In order for web applications to be gain traction over desktop
>> software, they must be able to interface with usb/RS232. I believe the
>> security trade off is worth it.
>> I also believe that the working group should make the device element
>> spec a high priority. If you don't google will probably implement
>> their own version for chrome OS(it will be necessary in a browser
>> based OS model).
>> Thanks,
>> Seth Brown
> Agreed. Access to RS232 data from scripts will promote the use of web
> technologies in new applications for the embedded market.
> --
> Diego

More information about the whatwg mailing list