A quick fix for Issue 18353....

A quick fix for Issue 18353.
This is my stupid mistake that I forgot removing the platform-dependent code in our renderer code.
This change just add defined(OS_MACOSX) instead of removing #ifdef blocks since they are used by Chrome OS.

BUG=18353
"Regression: Arrow Keys and Page Up/Down Keys Have No Affect"
TEST=Type an arrow key in a web page and see it scrolls the page.

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=22601

[Avi (use Gerrit), 2009-08-04 13:46:45]

I don't like the triple #ifdefs. When you say "used by chrome os", can't you say
!defined (whatever that is) rather than a || b || c?

[Avi (use Gerrit), 2009-08-04 14:00:37]

On 2009/08/04 13:46:45, Avi wrote:
> I don't like the triple #ifdefs. When you say "used by chrome os", can't you
say
> !defined (whatever that is) rather than a || b || c?

Actually, we've always done three platforms, and just let "Chrome OS" be a
variant of Linux. Do they really need different keyboard handling than normal
Linux?

[Hironori Bono, 2009-08-05 10:49:35]

Avi,

Thank you for your review and comments.
I misunderstood about Chrome OS and it is good to remove the #ifdef blocks.
Is it possible to review the updated one?

Regards,

On 2009/08/04 14:00:37, Avi wrote:
> On 2009/08/04 13:46:45, Avi wrote:
> > I don't like the triple #ifdefs. When you say "used by chrome os", can't you
> say
> > !defined (whatever that is) rather than a || b || c?
> 
> Actually, we've always done three platforms, and just let "Chrome OS" be a
> variant of Linux. Do they really need different keyboard handling than normal
> Linux?

[Avi (use Gerrit), 2009-08-05 14:05:35]

lgtm