Cleanup Javascript Style Violations for chrome://omnibox/

Cleanup Javascript Style Violations for chrome://omnibox/

Precisely, switch getElementById() to $()

BUG=
TEST=by hand, things still seem to work

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=136033

[Mark P, 2012-05-08 15:46:02]

Arv,

You should be able to easily rubber-stamp this.

--mark

[arv (Not doing code reviews), 2012-05-08 16:18:14]

LGTM

[commit-bot: I haz the power, 2012-05-08 16:25:48]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/mpearson@chromium.org/10382057/1

[commit-bot: I haz the power, 2012-05-08 16:53:56]

Try job failure for 10382057-1 on win for step "update".
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win&number...

Step "update" is always a major failure.
Look at the try server FAQ for more details.

[commit-bot: I haz the power, 2012-05-08 17:44:18]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/mpearson@chromium.org/10382057/1

[commit-bot: I haz the power, 2012-05-08 23:38:40]

Try job failure for 10382057-1 (retry) (retry) on win_rel for step
"browser_tests".
It's a second try, previously, step "browser_tests" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...

[Mark P, 2012-05-09 00:51:34]

On 2012/05/08 23:38:40, I haz the power (commit-bot) wrote:
> Try job failure for 10382057-1 (retry) (retry) on win_rel for step
> "browser_tests".
> It's a second try, previously, step "browser_tests" failed.
>
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...

Failures seem unconnected to the change.  Trying again.

[commit-bot: I haz the power, 2012-05-09 00:51:51]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/mpearson@chromium.org/10382057/1

[commit-bot: I haz the power, 2012-05-09 00:57:59]

Try job failure for 10382057-1 on win for step "update".
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win&number...

Step "update" is always a major failure.
Look at the try server FAQ for more details.

[commit-bot: I haz the power, 2012-05-09 01:22:19]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/mpearson@chromium.org/10382057/1

[commit-bot: I haz the power, 2012-05-09 05:23:48]

Try job failure for 10382057-1 (retry) (retry) on win_rel for step
"browser_tests".
It's a second try, previously, step "browser_tests" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...

[commit-bot: I haz the power, 2012-05-09 12:11:04]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/mpearson@chromium.org/10382057/1

[commit-bot: I haz the power, 2012-05-09 12:37:54]

Try job failure for 10382057-1 (retry) on win for step "update".
It's a second try, previously, step "runhooks" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win&number...

Step "update" is always a major failure.
Look at the try server FAQ for more details.

[commit-bot: I haz the power, 2012-05-09 12:44:10]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/mpearson@chromium.org/10382057/1

[commit-bot: I haz the power, 2012-05-09 15:07:11]

Try job failure for 10382057-1 (retry) on win_rel for step "browser_tests".
It's a second try, previously, step "browser_tests" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...

[Mark P, 2012-05-09 15:13:37]

On 2012/05/09 15:07:11, I haz the power (commit-bot) wrote:
> Try job failure for 10382057-1 (retry) on win_rel for step "browser_tests".
> It's a second try, previously, step "browser_tests" failed.
>
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...

F-ing commit queue.

I'll land this manually.

-m