Fix to proper error type on SpeechRecognition

Fix to proper error type on SpeechRecognition

Spec draft proposal : https://dvcs.w3.org/hg/speech-api/raw-file/tip/webspeechapi.html#speechreco-error

We need to add below error types.
- NOT_ALLOWED, SERVICE_NOT_ALLOWED, LANGUAGE_NOT_SUPPORTED
Also, We change to order of SpeechRecognitionError same as latest spec.

BUG=none

Committed: https://crrev.com/99db7e04583c04434aa10cdceb6df0612c51db96
Cr-Commit-Position: refs/heads/master@{#326240}

[deejay, 2015-04-08 16:28:14]

djmix.kim@samsung.com changed reviewers:
+ hans@chromium.org, tommi@chromium.org

[deejay, 2015-04-08 16:30:06]

Hi hans, tommi.
This patch is for fixing to proper error type on SpeechRecognition.
Please take a look!

Thanks.

[deejay, 2015-04-10 07:07:26]

On 2015/04/08 16:30:06, deejay wrote:
> Hi hans, tommi.
> This patch is for fixing to proper error type on SpeechRecognition.
> Please take a look!
> 
> Thanks.

Dear hans, tommi.
Could you review this patch?

[deejay, 2015-04-13 15:47:11]

djmix.kim@samsung.com changed reviewers:
+ dmazzoni@chromium.org, dtseng@chromium.org

[deejay, 2015-04-13 15:52:48]

+ add more reviewer.

Dear dmazzoni, dtseng.
Is it possible to review about patch for speech recognition?

[deejay, 2015-04-20 14:41:40]

On 2015/04/13 15:52:48, deejay wrote:
> + add more reviewer.
> 
> Dear dmazzoni, dtseng.
> Is it possible to review about patch for speech recognition?

Friendly ping.

[tommi (sloooow) - chröme, 2015-04-20 16:20:30]

lgtm

[gshires1, 2015-04-20 20:15:55]

lgtm

[deejay, 2015-04-21 01:22:17]

The CQ bit was checked by djmix.kim@samsung.com

[commit-bot: I haz the power, 2015-04-21 01:22:29]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1073513002/1

[commit-bot: I haz the power, 2015-04-21 01:31:06]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-04-21 01:31:08]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[deejay, 2015-04-21 06:16:21]

djmix.kim@samsung.com changed reviewers:
+ creis@chromium.org, davidben@chromium.org
- dmazzoni@chromium.org, dtseng@chromium.org

[deejay, 2015-04-21 06:20:37]

On 2015/04/21 01:31:08, I haz the power (commit-bot) wrote:
> Try jobs failed on following builders:
>   chromium_presubmit on tryserver.chromium.linux (JOB_FAILED,
>
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

This error was occured by missing LGTM.
--------------------------------------------------------
** Presubmit ERRORS **
Missing LGTM from an OWNER for these files:
    content/public/common/speech_recognition_error.h
    content/renderer/speech_recognition_dispatcher.cc
--------------------------------------------------------

Dear Charlie Reis and David Benjamin.
Please take a look this patch!

[Charlie Reis, 2015-04-21 17:04:49]

LGTM.

In the CL description, the BUG= line should point to a Chromium bug number, not
the spec URL.  Let's put the spec URL earlier in the CL description.  It looks
like 116954 is the relevant bug number.

Also s/lastest/latest/

[deejay, 2015-04-22 05:56:37]

On 2015/04/21 17:04:49, Charlie Reis wrote:
> LGTM.
> 
> In the CL description, the BUG= line should point to a Chromium bug number,
not
> the spec URL.  Let's put the spec URL earlier in the CL description.  It looks
> like 116954 is the relevant bug number.
> 
> Also s/lastest/latest/

Thanks for reviewing!
I've updated on commit msg.

[deejay, 2015-04-22 05:56:55]

The CQ bit was checked by djmix.kim@samsung.com

[commit-bot: I haz the power, 2015-04-22 05:57:07]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1073513002/1

[commit-bot: I haz the power, 2015-04-22 07:23:20]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-04-22 07:24:12]

Patchset 1 (id:??) landed as
https://crrev.com/99db7e04583c04434aa10cdceb6df0612c51db96
Cr-Commit-Position: refs/heads/master@{#326240}

[Charlie Reis, 2015-04-22 16:44:31]

On 2015/04/22 05:56:37, deejay wrote:
> On 2015/04/21 17:04:49, Charlie Reis wrote:
> > LGTM.
> > 
> > In the CL description, the BUG= line should point to a Chromium bug number,
> not
> > the spec URL.  Let's put the spec URL earlier in the CL description.  It
looks
> > like 116954 is the relevant bug number.
> > 
> > Also s/lastest/latest/
> 
> Thanks for reviewing!
> I've updated on commit msg.

I asked you to use 116954 on the BUG line.  Too late to fix it now, but please
try to list an actual bug number in future CLs.

[deejay, 2015-04-23 02:09:08]

On 2015/04/22 16:44:31, Charlie Reis wrote:
> On 2015/04/22 05:56:37, deejay wrote:
> > On 2015/04/21 17:04:49, Charlie Reis wrote:
> > > LGTM.
> > > 
> > > In the CL description, the BUG= line should point to a Chromium bug
number,
> > not
> > > the spec URL.  Let's put the spec URL earlier in the CL description.  It
> looks
> > > like 116954 is the relevant bug number.
> > > 
> > > Also s/lastest/latest/
> > 
> > Thanks for reviewing!
> > I've updated on commit msg.
> 
> I asked you to use 116954 on the BUG line.  Too late to fix it now, but please
> try to list an actual bug number in future CLs.

Dear Charlie Reis.

Sorry!
I've miss understanding.

If I have similar updating after, I will fill BUG id in commit msg.