<rdar://problem/
3976314> REGRESSION (180-TOT): submitting password fields fail on Panther
* kwq/KWQTextField.mm: (-[KWQTextFieldController string]): on panther, the secure text field's editor
does not contain the real string, so now we just call stringValue on the field in that case.
git-svn-id: https://svn.webkit.org/repository/webkit/trunk@8468
268f45cc-cd09-0410-ab3c-
d52691b4dbfc
+2005-01-27 Adele Amchan <adele@apple.com>
+
+ fixed by Darin, reviewed by me.
+
+ <rdar://problem/3976314> REGRESSION (180-TOT): submitting password fields fail on Panther
+
+ * kwq/KWQTextField.mm: (-[KWQTextFieldController string]): on panther, the secure text field's editor
+ does not contain the real string, so now we just call stringValue on the field in that case.
+
2005-01-26 Maciej Stachowiak <mjs@apple.com>
Reviewed by Darin, Hyatt and Ken.
- (NSString *)string
{
+#if BUILDING_ON_PANTHER
+ // On Panther, the secure text field's editor does not contain the real
+ // string, so we must always call stringValue on the field. We'll live
+ // with the side effect of ending International inline input for these
+ // password fields on Panther only, since it's fixed in Tiger.
+ if ([field isKindOfClass:[NSSecureTextField class]]) {
+ return [field stringValue];
+ }
+#endif
// Calling stringValue can have a side effect of ending International inline input.
// So don't call it unless there's no editor.
NSText *editor = [field _KWQ_currentEditor];