Bug 133196 - Can't type in status in facebook.com on iOS Safari because keyboard disappears
Summary: Can't type in status in facebook.com on iOS Safari because keyboard disappears
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: UI Events (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Ryosuke Niwa
URL:
Keywords:
Depends on:
Blocks: 29241
  Show dependency tree / graph
 
Reported: 2014-05-22 17:58 PDT by Ryosuke Niwa
Modified: 2014-05-23 00:35 PDT (History)
8 users (show)

See Also:

Attachments
Patch (8.29 KB, patch)
2014-05-22 18:05 PDT, Ryosuke Niwa 		no flags Details | Formatted Diff | Diff
Patch for landing (8.34 KB, patch)
2014-05-22 20:27 PDT, Ryosuke Niwa 		no flags Details | Formatted Diff | Diff
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ryosuke Niwa 2014-05-22 17:58:11 PDT 
With the latest WebKit, we can't type in status on facebook.com because the keyboard disappears as you tap on "Update Status".
Comment 1 Ryosuke Niwa 2014-05-22 18:05:27 PDT 
Created attachment 231927 [details]
Patch
Comment 2 Geoffrey Garen 2014-05-22 18:59:49 PDT 
Comment on attachment 231927 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=231927&action=review

r=me

> Source/WebCore/ChangeLog:8
> +        When the user taps on the status on facebook.com, the page focuses an textarea,

"a"

> Source/WebCore/ChangeLog:9
> +        which is then made momentarily visible by setting display:none.

"invisible"?
Comment 3 Ryosuke Niwa 2014-05-22 20:27:24 PDT 
Created attachment 231936 [details]
Patch for landing
Comment 4 WebKit Commit Bot 2014-05-22 21:06:35 PDT 
Comment on attachment 231936 [details]
Patch for landing

Clearing flags on attachment: 231936

Committed r169244: <http://trac.webkit.org/changeset/169244>
Comment 5 WebKit Commit Bot 2014-05-22 21:06:40 PDT 
All reviewed patches have been landed.  Closing bug.
Comment 6 Arunprasad 2014-05-22 22:05:29 PDT 
Actually bug 29241 is almost same like https://chromium.googlesource.com/chromium/blink/+/c58f636fd18fc27944c42e27d6a92a36867c57e1.

Is it happening on Chrome also?(I mean Chrome for Android/iOS?)
Comment 7 Ryosuke Niwa 2014-05-23 00:35:12 PDT 
(In reply to comment #6)
> Actually bug 29241 is almost same like https://chromium.googlesource.com/chromium/blink/+/c58f636fd18fc27944c42e27d6a92a36867c57e1.
> 
> Is it happening on Chrome also?(I mean Chrome for Android/iOS?)

I don't know.  But that's somewhat irrelevant because the content served to Android/Chrome might be different from the one served to iOS/Safari.

As I see it, the specification is incompatible with the Web today.