799029 - [keyboard] Cursor cannot be positioned by the user

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Gaia::Keyboard, defect)

Description

[Jose Manuel Cantera]

Go to the FB Import login page. start editing the user name and then try to reposition the cursor in between the provided letters. The cursor cannot be positioned and you need to reset the entire content to amend it.

Comment 1

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

haven't found the dup.  closest thing I came was bug 225109 so far.  :|

Comment 2

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

bug 652168 and bug 795045... they are only for FF for android?

Comment 3

[Mark Finkle (:mfinkle) (use needinfo?)]

Blocking on this bug until we find a b2g platform bug.

Comment 4

[Chris Peterson [:cpeterson]]

(In reply to Jose M. Cantera from comment #0)
> Go to the FB Import login page. start editing the user name and then try to
> reposition the cursor in between the provided letters. The cursor cannot be
> positioned and you need to reset the entire content to amend it.

Jose, by "FB Import login page", do you mean the Contacts app's "Import from Facebook" login?

Comment 5

[Chris Peterson [:cpeterson]]

I can reproduce the problem on my Otoro phone, but not the B2G Desktop build. I see the following interesting error messages when I type in the "Import from Facebook" text fields (on the B2G Desktop):

JS Component Loader: ERROR chrome://browser/content/forms.js:242
                     NS_ERROR_INVALID_POINTER: Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIMessageSender.sendAsyncMessage]

JS Component Loader: ERROR chrome://browser/content/forms.js:242
                     NS_ERROR_INVALID_POINTER: Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIMessageSender.sendAsyncMessage]

JavaScript error: chrome://browser/content/forms.js, line 50: can't access dead object
JavaScript error: chrome://browser/content/forms.js, line 50: can't access dead object
JavaScript error: chrome://browser/content/forms.js, line 50: can't access dead object
JavaScript error: chrome://browser/content/forms.js, line 50: can't access dead object
JavaScript error: chrome://browser/content/forms.js, line 50: can't access dead object

Comment 6

[Aaron Train [:aaronmt]]

'New Tweet' dialog box too on Twitter is another case

Comment 7

[Chris Peterson [:cpeterson]]

This bug is not specific to B2G. I can reproduce the Facebook login bug [1] on Firefox for Android. I can reproduce the Twitter tweet bug [2] with both Firefox for Android and desktop!

[1] https://m.facebook.com/
[2] https://mobile.twitter.com/compose/tweet

Comment 8

[Chris Peterson [:cpeterson]]

I think these are content bugs. I will open evangelism bugs for these issues:

1. Bug 814274: Twitter's CSS specifies "-moz-user-select:none", which regrettably behaves differently from "-webkit-user-select:none". Twitter should use "-moz-user-select:-moz-none".

2. Facebook sends us non-touch aware CSS because they do not recognize our Gecko User-Agent string. If I send a WebKit User-Agent string, then Facebook sends us a page that works correctly.

Comment 9

[Jose Manuel Cantera]

(In reply to Chris Peterson (:cpeterson) from comment #8)
> I think these are content bugs. I will open evangelism bugs for these issues:
> 

> 2. Facebook sends us non-touch aware CSS because they do not recognize our
> Gecko User-Agent string. If I send a WebKit User-Agent string, then Facebook
> sends us a page that works correctly.

That's not true. Actually, for Facebook, B2G sends a Webkit-Android like UA String and Facebook recognizes us as an Android device. And the proof is that they offer the possibility of downloading the Android app (see attached capture). Maybe even in that case their mark-up is wrong but that's another story.

Comment 10

[Jose Manuel Cantera]

Attachment: screen capture for Facebook

Comment 11

[Chris Peterson [:cpeterson]]

(In reply to Jose M. Cantera from comment #9)
> That's not true. Actually, for Facebook, B2G sends a Webkit-Android like UA
> String and Facebook recognizes us as an Android device. And the proof is
> that they offer the possibility of downloading the Android app (see attached
> capture). Maybe even in that case their mark-up is wrong but that's another
> story.

oops. You are correct, Jose. I had overlooked Gaia's ua-override-prefs.js.

With the correct User-Agent string for facebook.com, I see the same problem we have on mobile.twitter.com: bug 814274. Facebook's CSS is preventing input text selection by using "-moz-user-select:none", which behaves differently from "-webkit-user-select:none".

Comment 12

[Wesley Johnston (:wesj)]

I'm not sure this is evang. Should user-select be affecting the ability to position the cursor? Our own docs read like it just affects selection.

Comment 13

[Chris Peterson [:cpeterson]]

(In reply to Wesley Johnston (:wesj) from comment #12)
> I'm not sure this is evang. Should user-select be affecting the ability to
> position the cursor? Our own docs read like it just affects selection.

wesj, -moz-user-select affects positioning of the cursor using the mouse (and touch), but not the keyboard. For example, if I use Firefox's Page Inspector to add -moz-user-select:none to this Bugzilla textarea, I can no longer position the cursor with my mouse. Perhaps this is a bug in -moz-user-select's implementation (or docs).

Comment 14

[Chris Peterson [:cpeterson]]

I opened bug 816298 to investigate changing "-moz-user-select:none" to behave like WebKit, IE, and Opera (and "-moz-user-select:-moz-none"). That change would fix these Twitter and Facebook bugs.

Comment 15

[Alex Keybl [:akeybl]]

This issue is found on other Mozilla platforms and can be worked around by deleting the inputted characters and re-inputting.

Comment 16

[Chris Peterson [:cpeterson]]

This bug has been fixed in Gecko 21.

Comment 17

[Lukas Blakk [:lsblakk] use ?needinfo]

Batch edit: Bugs marked status-b2g18: affected after 2/13 branching of v1.0.1 are now also status-b2g18-v1.0.1: affected