Index: chrome/browser/ui/views/autofill/autofill_dialog_views.cc |
diff --git a/chrome/browser/ui/views/autofill/autofill_dialog_views.cc b/chrome/browser/ui/views/autofill/autofill_dialog_views.cc |
index 15e9a028867d27f88d00753024ab04bbd2f70fcb..c8c91afc5695bf066c711242062dd30b96d52aff 100644 |
--- a/chrome/browser/ui/views/autofill/autofill_dialog_views.cc |
+++ b/chrome/browser/ui/views/autofill/autofill_dialog_views.cc |
@@ -1694,11 +1694,11 @@ void AutofillDialogViews::ContentsChanged(views::Textfield* sender, |
bool AutofillDialogViews::HandleKeyEvent(views::Textfield* sender, |
const ui::KeyEvent& key_event) { |
- scoped_ptr<ui::KeyEvent> copy(key_event.Copy()); |
+ ui::KeyEvent copy(key_event); |
#if defined(OS_WIN) && !defined(USE_AURA) |
Evan Stade
2013/12/02 19:16:39
Q: when can we get rid of this?
sadrul
2013/12/02 19:21:29
My best guess is sometime after win-aura goes stab
|
- content::NativeWebKeyboardEvent event(copy->native_event()); |
+ content::NativeWebKeyboardEvent event(copy.native_event()); |
#else |
- content::NativeWebKeyboardEvent event(copy.get()); |
+ content::NativeWebKeyboardEvent event(©); |
#endif |
return delegate_->HandleKeyPressEventInInput(event); |
} |