WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
80019
Speech JavaScript API: compile- and runtime flags
https://bugs.webkit.org/show_bug.cgi?id=80019
Summary
Speech JavaScript API: compile- and runtime flags
Hans Wennborg
Reported
2012-03-01 04:03:56 PST
Implement Speech JavaScript API
Attachments
Patch
(136.49 KB, patch)
2012-03-01 04:11 PST
,
Hans Wennborg
no flags
Details
Formatted Diff
Diff
Patch
(36.97 KB, patch)
2012-03-01 05:53 PST
,
Hans Wennborg
no flags
Details
Formatted Diff
Diff
Show Obsolete
(1)
View All
Add attachment
proposed patch, testcase, etc.
Hans Wennborg
Comment 1
2012-03-01 04:11:51 PST
Created
attachment 129679
[details]
Patch
WebKit Review Bot
Comment 2
2012-03-01 04:15:33 PST
Please wait for approval from
fishd@chromium.org
before submitting because this patch contains changes to the Chromium public API. Thanks for the patch. If this patch contains new public API please make sure it follows the guidelines for new WebKit2 GTK+ API. See
http://trac.webkit.org/wiki/WebKitGTK/AddingNewWebKit2API
Hans Wennborg
Comment 3
2012-03-01 05:53:57 PST
Created
attachment 129689
[details]
Patch Let's add the compile- and runtime flags first to make this more reviewable.
WebKit Review Bot
Comment 4
2012-03-01 05:57:44 PST
Attachment 129689
[details]
did not pass style-queue: Failed to run "['Tools/Scripts/check-webkit-style', '--diff-files', u'ChangeLog', u'LayoutTests/ChangeLog', u'La..." exit_code: 1 WARNING: File exempt from style guide. Skipping: "Source/WebKit2/UIProcess/API/gtk/WebKitDefines.h" Source/WebKit2/WebProcess/gtk/WebProcessMainGtk.cpp:71: Use 0 instead of NULL. [readability/null] [5] Total errors found: 1 in 166 files If any of these errors are false positives, please file a bug against check-webkit-style.
Adam Barth
Comment 5
2012-03-03 15:34:12 PST
Comment on
attachment 129689
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=129689&action=review
> Source/WebCore/bindings/generic/RuntimeEnabledFeatures.h:157 > +#if ENABLE(SCRIPTED_SPEECH) > + static void setScriptedSpeechEnabled(bool isEnabled) { isScriptedSpeechEnabled = isEnabled; } > + static bool scriptedSpeechEnabled() { return isScriptedSpeechEnabled; } > + static bool webkitSpeechRecognitionEnabled() { return isScriptedSpeechEnabled; } > + static bool webkitSpeechRecognitionErrorEnabled() { return isScriptedSpeechEnabled; } > + static bool webkitSpeechGrammarEnabled() { return isScriptedSpeechEnabled; } > + static bool webkitSpeechGrammarListEnabled() { return isScriptedSpeechEnabled; } > +#endif
This change is slightly ahead of what you need in this patch.
Satish Sampath
Comment 6
2012-03-03 16:27:10 PST
Comment on
attachment 129689
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=129689&action=review
Tools/Scripts/build-webkit: line 98
> $scriptedSpeechSupport
I see the rest of this list is alphabetically sorted and I understand $scriptedSpeechSupport is placed next to $inputSpeechSupport. But since in the long term $inputSpeechSupport should be going away so it may make sense to insert $scriptedSpeechSupport in the right alphabetical order instead of the current location. Same for ENABLE_SCRIPTED_SPEECH in lines 232-234
>> Source/WebCore/bindings/generic/RuntimeEnabledFeatures.h:157 >> +#endif > > This change is slightly ahead of what you need in this patch.
I think Hans's idea was to have this patch start both the compile time and runtime flags for the feature. In that sense may be the first 2 in the above list make sense but the rest could be added in subsequent patches where they are required.
Adam Barth
Comment 7
2012-03-03 17:00:34 PST
It's not a big deal either way.
WebKit Review Bot
Comment 8
2012-03-03 17:06:25 PST
Comment on
attachment 129689
[details]
Patch Clearing flags on attachment: 129689 Committed
r109667
: <
http://trac.webkit.org/changeset/109667
>
WebKit Review Bot
Comment 9
2012-03-03 17:06:32 PST
All reviewed patches have been landed. Closing bug.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug