A quick fix for Issue 26880....

chrome/browser/renderer_host/render_widget_host_view_mac.mm

 // Copyright (c) 2006-2008 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "chrome/browser/renderer_host/render_widget_host_view_mac.h"
 
+#import <Carbon/Carbon.h>
+#include <ApplicationServices/ApplicationServices.h>
+#include <AvailabilityMacros.h>
+
 #include "base/histogram.h"
 #import "base/scoped_nsobject.h"
 #include "base/string_util.h"
 #include "base/sys_string_conversions.h"
 #include "chrome/browser/browser_trial.h"
 #import "chrome/browser/cocoa/rwhvm_editcommand_helper.h"
 #include "chrome/browser/renderer_host/backing_store.h"
 #include "chrome/browser/renderer_host/render_process_host.h"
 #include "chrome/browser/renderer_host/render_widget_host.h"
 #include "chrome/browser/spellchecker_platform_engine.h"
@@ skipping 208 matching lines @@
 }
 
 void RenderWidgetHostViewMac::SetIsLoading(bool is_loading) {
   is_loading_ = is_loading;
   UpdateCursorIfOverSelf();
 }
 
 void RenderWidgetHostViewMac::IMEUpdateStatus(int control,
                                               const gfx::Rect& caret_rect) {
   // The renderer updates its IME status.
-  // We need to control the input method according to the given message.
+#if MAC_OS_X_VERSION_MIN_REQUIRED <= MAC_OS_X_VERSION_10_5
+  // Complete the ongoing composition when a renderer finishes it.
+  // We need to use Carbon APIs to finish an ongoing composition since Leopard
+  // doesn't implement a Cocoa API -[NSTextInputContext discardMarkedText:]
+  // that discards the marked text.
+  if (control == IME_DISABLE || control == IME_COMPLETE_COMPOSITION)
+    ::FixTSMDocument(::TSMGetActiveDocument());
+#endif
 
   // We need to convert the coordinate of the cursor rectangle sent from the
   // renderer and save it. Our IME backend uses a coordinate system whose
   // origin is the upper-left corner of this view. On the other hand, Cocoa
   // uses a coordinate system whose origin is the lower-left corner of this
   // view. So, we convert the cursor rectangle and save it.
   NSRect view_rect = [cocoa_view_ bounds];
   const int y_offset = static_cast<int>(view_rect.size.height);
   im_caret_rect_ = NSMakeRect(caret_rect.x(),
                               y_offset - caret_rect.y() - caret_rect.height(),
@@ skipping 320 matching lines @@
 
 - (BOOL)performKeyEquivalent:(NSEvent*)theEvent {
   if (ignoreKeyEvents_)
     return NO;
 
   // |performKeyEquivalent:| is sent to all views of a window, not only down the
   // responder chain (cf. "Handling Key Equivalents" in
   // http://developer.apple.com/mac/library/documentation/Cocoa/Conceptual/EventOverview/HandlingKeyEvents/HandlingKeyEvents.html
   // ). We only want to handle key equivalents if we're first responder.
   if ([[self window] firstResponder] != self)
-    return NO;  
+    return NO;
 
-  // If we return |NO| from this function, cocoa will send the key event to     
-  // the menu and only if the menu does not process the event to |keyDown:|. We 
-  // want to send the event to a renderer _before_ sending it to the menu, so   
-  // we need to return |YES| for all events that might be swallowed by the menu.        
-  // We do not return |YES| for every keypress because we don't get |keyDown:|  
-  // events for keys that we handle this way.   
-  NSUInteger modifierFlags = [theEvent modifierFlags];  
-  if ((modifierFlags & NSCommandKeyMask) == 0) {        
-    // Make sure the menu does not contain key equivalents that don't   
-    // contain cmd.     
-    DCHECK(![[NSApp mainMenu] performKeyEquivalent:theEvent]);  
-    return NO;  
+  // If we return |NO| from this function, cocoa will send the key event to
+  // the menu and only if the menu does not process the event to |keyDown:|. We
+  // want to send the event to a renderer _before_ sending it to the menu, so
+  // we need to return |YES| for all events that might be swallowed by the menu.
+  // We do not return |YES| for every keypress because we don't get |keyDown:|
+  // events for keys that we handle this way.
+  NSUInteger modifierFlags = [theEvent modifierFlags];
+  if ((modifierFlags & NSCommandKeyMask) == 0) {
+    // Make sure the menu does not contain key equivalents that don't
+    // contain cmd.
+    DCHECK(![[NSApp mainMenu] performKeyEquivalent:theEvent]);
+    return NO;
   }
 
-  // Command key combinations are sent via performKeyEquivalent rather than     
-  // keyDown:. We just forward this on and if WebCore doesn't want to handle    
-  // it, we let the TabContentsView figure out how to reinject it.      
-  [self keyEvent:theEvent wasKeyEquivalent:YES];        
+  // Command key combinations are sent via performKeyEquivalent rather than
+  // keyDown:. We just forward this on and if WebCore doesn't want to handle
+  // it, we let the TabContentsView figure out how to reinject it.
+  [self keyEvent:theEvent wasKeyEquivalent:YES];
   return YES;
 }
 
 - (BOOL)_wantsKeyDownForEvent:(NSEvent*)event {
   // This is a SPI that AppKit apparently calls after |performKeyEquivalent:|
   // returned NO. If this function returns |YES|, Cocoa sends the event to
   // |keyDown:| instead of doing other things with it. Ctrl-tab will be sent
   // to us instead of doing key view loop control, ctrl-left/right get handled
   // correctly, etc.
   // (However, there are still some keys that Cocoa swallows, e.g. the key
   // equivalent that Cocoa uses for toggling the input langauge. In this case,
   // that's actually a good thing, though -- see http://crbug.com/26115 .)
   return YES;
 }
 
 - (void)keyEvent:(NSEvent*)theEvent {
-  [self keyEvent:theEvent wasKeyEquivalent:NO]; 
-}       
+  [self keyEvent:theEvent wasKeyEquivalent:NO];
+}
 
-- (void)keyEvent:(NSEvent *)theEvent wasKeyEquivalent:(BOOL)equiv {     
+- (void)keyEvent:(NSEvent *)theEvent wasKeyEquivalent:(BOOL)equiv {
   if (ignoreKeyEvents_)
     return;
 
-  DCHECK([theEvent type] != NSKeyDown ||        
+  DCHECK([theEvent type] != NSKeyDown ||
          !equiv == !([theEvent modifierFlags] & NSCommandKeyMask));
 
   scoped_nsobject<RenderWidgetHostViewCocoa> keepSelfAlive([self retain]);
 
   // Don't cancel child popups; the key events are probably what's triggering
   // the popup in the first place.
 
   NativeWebKeyboardEvent event(theEvent);
 
   // Save the modifier keys so the insertText method can use it when it sends
@@ skipping 709 matching lines @@
                                  base::Time::Now().ToDoubleT());
     renderWidgetHostView_->render_widget_host_->ForwardKeyboardEvent(event);
   } else {
     renderWidgetHostView_->render_widget_host_->ImeConfirmComposition(
         UTF8ToUTF16([im_text UTF8String]));
   }
   renderWidgetHostView_->im_composing_ = false;
 }
 
 @end