[webkit-dev] Feature Announcement: WebSpeech - Speech Synthesis
Hello, I'm planning on implementing the speech synthesis aspect of the WebSpeech API Specification https://dvcs.w3.org/hg/speech-api/raw-file/tip/speechapi.html#tts-section The WebKit bug can be found here https://bugs.webkit.org/show_bug.cgi?id=106742 I'll be putting the files in the Modules/speech/ directory where the WebSpeech Speech Recognition files live, but I'll be using a different ENABLE flag so that a platform can decide to support one or the other (or both). The flag I plan on using is WEB_SPEECH_SYNTHESIS Let me know if you have any questions. Thanks ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] SVG external referencing not working as of latest chrome canary
Hi all, I've done a little experimenting to see where we're at wrt to svg feature set and it seems webkit is lagging some way behind gecko. Of particular concern is lack of external referencing capability through the svg use tag. I attach a simple example that works in firefox for your consideration. root.svg should link through to object.svg and render it. It doesn't in latest chrome canary. You've had a bug filed on this for a long time but it's still unresolved so thought I'd mail. https://bugs.webkit.org/show_bug.cgi?id=12499 We are lowering the priority because this is not heavily used. The feature is not used heavily because it doesn't work properly. Never use lack of use as a reason to not do something :) SVG is important because it's the lowest common denominator high spec graphics interface across all major browsers. Looks like you're behind ie9 in terms of implementation. You should at least match their implementation so we can raise the bar. Of course IE should implement webgl but until they do SVG is the best we've got across all mainstream browsers. Thanks in advance for your consideration. webkit is behind the curve in implementation of this web standard - please address this. Best regards, Steve Williams attachment: root.svgattachment: object.svg___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] SVG external referencing not working as of latest chrome canary
Hi Steve, If you're interested in more complete SVG support, here are some things you can do: (1) File bugs for any missing features that don't have bugs already. (2) Create a meta-bug for complete SVG 1.1 support or what have you that's blocked by all the relevant feature bugs. (3) Add useful reduced test cases to the relevant bugs. (4) Cite real-world sites using the functionality to the relevant bugs. (5) Work on implementing some of these features yourself. (6) Persuade WebKit hackers that you know (offlist) to work on some of these features. (7) Contact one of the vendors that works on WebKit via their developer relations channels and ask them to implement the features you care about. If you are interested in more complete SVG support, I encourage you to do some or all of these things. Note, however, that posting feature requests or advocacy for specific bugs is not really appropriate for this list. It's for talking about the development of WebKit itself, and no one uses requests on this list as a way to drive priorities. I'm glad to see you are interested in WebKit's SVG support and I hope you will consider some of the possible steps above to improve it. Cheers, Maciej On Jan 13, 2013, at 8:37 AM, Steve Williams stephen.j.h.willi...@googlemail.com wrote: Hi all, I've done a little experimenting to see where we're at wrt to svg feature set and it seems webkit is lagging some way behind gecko. Of particular concern is lack of external referencing capability through the svg use tag. I attach a simple example that works in firefox for your consideration. root.svg should link through to object.svg and render it. It doesn't in latest chrome canary. You've had a bug filed on this for a long time but it's still unresolved so thought I'd mail. https://bugs.webkit.org/show_bug.cgi?id=12499 We are lowering the priority because this is not heavily used. The feature is not used heavily because it doesn't work properly. Never use lack of use as a reason to not do something :) SVG is important because it's the lowest common denominator high spec graphics interface across all major browsers. Looks like you're behind ie9 in terms of implementation. You should at least match their implementation so we can raise the bar. Of course IE should implement webgl but until they do SVG is the best we've got across all mainstream browsers. Thanks in advance for your consideration. webkit is behind the curve in implementation of this web standard - please address this. Best regards, Steve Williams root.svgobject.svg___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Feature Announcement: WebSpeech - Speech Synthesis
On Sun, Jan 13, 2013 at 2:12 AM, Chris Fleizach cfleiz...@apple.com wrote: I'm planning on implementing the speech synthesis aspect of the WebSpeech API Specification https://dvcs.w3.org/hg/speech-api/raw-file/tip/speechapi.html#tts-section [...] Let me know if you have any questions. Completely out of curiosity: How does the voiceURI attribute works? Is there some kind of standard for voices? Benjamin ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] SVG external referencing not working as of latest chrome canary
I believe https://bugs.webkit.org/show_bug.cgi?id=91237 is the bug you're looking for. I've CC'd relevant chrome folks. As Maciej notes, webkit-dev isn't really the place for bug reports. :) It's a mailing list of over 2000 people. Most of whom don't care about specific SVG bugs. Regardless, thanks for the report. Please take further discussion to the bugs system. -eric On Sun, Jan 13, 2013 at 1:37 PM, Maciej Stachowiak m...@apple.com wrote: Hi Steve, If you're interested in more complete SVG support, here are some things you can do: (1) File bugs for any missing features that don't have bugs already. (2) Create a meta-bug for complete SVG 1.1 support or what have you that's blocked by all the relevant feature bugs. (3) Add useful reduced test cases to the relevant bugs. (4) Cite real-world sites using the functionality to the relevant bugs. (5) Work on implementing some of these features yourself. (6) Persuade WebKit hackers that you know (offlist) to work on some of these features. (7) Contact one of the vendors that works on WebKit via their developer relations channels and ask them to implement the features you care about. If you are interested in more complete SVG support, I encourage you to do some or all of these things. Note, however, that posting feature requests or advocacy for specific bugs is not really appropriate for this list. It's for talking about the development of WebKit itself, and no one uses requests on this list as a way to drive priorities. I'm glad to see you are interested in WebKit's SVG support and I hope you will consider some of the possible steps above to improve it. Cheers, Maciej On Jan 13, 2013, at 8:37 AM, Steve Williams stephen.j.h.willi...@googlemail.com wrote: Hi all, I've done a little experimenting to see where we're at wrt to svg feature set and it seems webkit is lagging some way behind gecko. Of particular concern is lack of external referencing capability through the svg use tag. I attach a simple example that works in firefox for your consideration. root.svg should link through to object.svg and render it. It doesn't in latest chrome canary. You've had a bug filed on this for a long time but it's still unresolved so thought I'd mail. https://bugs.webkit.org/show_bug.cgi?id=12499 We are lowering the priority because this is not heavily used. The feature is not used heavily because it doesn't work properly. Never use lack of use as a reason to not do something :) SVG is important because it's the lowest common denominator high spec graphics interface across all major browsers. Looks like you're behind ie9 in terms of implementation. You should at least match their implementation so we can raise the bar. Of course IE should implement webgl but until they do SVG is the best we've got across all mainstream browsers. Thanks in advance for your consideration. webkit is behind the curve in implementation of this web standard - please address this. Best regards, Steve Williams root.svgobject.svg___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Constructors for DOM4 Events
Seems fine to me. -Sam On Jan 10, 2013, at 6:36 AM, Kentaro Hara hara...@chromium.org wrote: At TPAC there was no objection for DOM4 Event constructors (e.g. new MouseEvent()). Now DOM4 Event constructors are on editor's draft: http://html5labs.interoperabilitybridges.com/dom4events/ https://dvcs.w3.org/hg/d4e/raw-file/tip/source_respec.htm Given the above, I am planning to implement them in WebKit (without any flag). If you have any concern, please let me know. Best Regards On Mon, Oct 1, 2012 at 7:44 AM, Kentaro Hara hara...@chromium.org wrote: Since TPAC is less than a month away, I don't understand why we can't wait for that discussion. Sounds reasonable. I'll wait for TPAC. I do support the idea in general, and I plan to be at TPAC and will advocate for it. I'll be also going to TPAC. I would appreciate your support. On Mon, Oct 1, 2012 at 2:11 PM, Maciej Stachowiak m...@apple.com wrote: Since TPAC is less than a month away, I don't understand why we can't wait for that discussion. I do support the idea in general, and I plan to be at TPAC and will advocate for it. I understand that sometimes we need to move ahead of the spec. If there's a reason not to wait a few extra weeks in this case, then please at least use a prefix. Cheers, Maciej On Sep 30, 2012, at 6:32 PM, Kentaro Hara hara...@chromium.org wrote: TL;DR: Would it be OK to implement constructors for DOM4 Events in WebKit without waiting for the spec? == Background == Events should have constructors. 'new XXXEvent()' is much easier than 'e = document.createEvent(...); e.initXXXEvent(_a_lot_of_arguments_)'. We have already implemented constructors for a bunch of Events such as Event, CustomEvent, ProgressEvent, etc [5]. However, we have not yet implemented constructors for DOM4 Events (i.e. UIEvent, MouseEvent, KeyboardEvent, WheelEvent, TextEvent, CompositionEvent) because they are not yet speced. Recently PointerEvent was speced with [Constructor] [2]. Considering that PointerEvent inherits MouseEvent, now we want to support [Constructor] on MouseEvent too. In terms of implementation, it is possible to implement [Constructor] on PointerEvent without implementing [Constructor] on MouseEvent. However, implementing [Constructor] on both PointerEvent and MouseEvent would be best. == Rationale for implementing constructors for DOM4 Events == I have been discussing this topic for one year, in www-dom@ [4] and a www.w3.org bug [3]. It looks like there is a consensus on introducing constructors for DOM4 Events. However, the spec is still a draft [1] and the www.w3.org bug [3] is marked as LATER. Last week I discussed the timeline of the spec with Jacob Rossi (a.k.a. a spec author of PointerEvent and DOM4 Events). According to him: - Their primary focus is on finishing DOM3 Events first. - With DOM3 Events in Candidate Recommendation, they are going to start working on the DOM4 Events. They will discuss it in TPAC. - They will introduce constructors to DOM4 Events. In summary, constructors for DOM4 Events are going to be speced, but it will take time. So I would like to implement them in WebKit a bit ahead of the spec (and thus implement PointerEvent constructors too). If you have any concern, please let me know. == References == [1] The spec draft by Jacob Rossi: http://html5labs.interoperabilitybridges.com/dom4events/ [2] The spec of Pointer Events: http://www.w3.org/Submission/pointer-events/ [3] www.w3.org bug: https://www.w3.org/Bugs/Public/show_bug.cgi?id=14051 [4] Discussion on www-dom@: http://lists.w3.org/Archives/Public/www-dom/2011OctDec/0081.html http://lists.w3.org/Archives/Public/www-dom/2012JanMar/0025.html [5] WebKit bug: https://bugs.webkit.org/show_bug.cgi?id=67824 -- Kentaro Hara, Tokyo, Japan (http://haraken.info) ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev -- Kentaro Hara, Tokyo, Japan (http://haraken.info) -- Kentaro Hara, Tokyo, Japan ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Feature Announcement: WebSpeech - Speech Synthesis
On Sun, Jan 13, 2013 at 2:10 PM, Benjamin Poulain benja...@webkit.orgwrote: On Sun, Jan 13, 2013 at 2:12 AM, Chris Fleizach cfleiz...@apple.com wrote: I'm planning on implementing the speech synthesis aspect of the WebSpeech API Specification https://dvcs.w3.org/hg/speech-api/raw-file/tip/speechapi.html#tts-section [...] Let me know if you have any questions. Completely out of curiosity: How does the voiceURI attribute works? Is there some kind of standard for voices? There's no standard (yet). A client is supposed to call getVoices() to get a list of possible voices, and the voiceURI is a unique identifier for each one. - Dominic ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev