1300739 - Firefox for Android caches user entered value of an input field

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: General, defect)

Description

[Bart]

User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36

Steps to reproduce:

JS fiddle: 
https://jsfiddle.net/planetbartoski/zsjLd21w/

Device Name: Samsung Galaxy S7
Model Number: SM-G930F
Android Version: 6.0.1
Mozilla Firefox 48.0

Step 0
---------- 
Touch the input field for the keyboard to come up

Step 1
---------- 
Type '1'

Step 2
---------- 
Type '2'



Actual results:

Step 1
---------- 
Output:
1. Alert content: '1'
2. Alert content: 'new input'

Step 2
---------
Output:
1. Alert content: '12'
2. Alert content: 'new input'

---------
If you start typing letters rather than numbers then all of the above outputs get duplicated


Expected results:

Step 1
---------- 
Output:
1. Alert content: '1'

Step 2
---------
Output:
1. Alert content: 'new input2'

Comment 1

[Loic]

I guess it's for the Android version of Firefox. Desktop doesn't have the issue.

Comment 2

[Bart]

Yes, we've managed to replicated only on FF for Android on Samsung S7:

Device Name: Samsung Galaxy S7
Model Number: SM-G930F
Android Version: 6.0.1
Mozilla Firefox 48.0

Comment 3

[Alex Caziuc]

I was able able to reproduce this using Samsung S7(6.0.1) on 48 Release. I get a different result than you but it's not the expected one.

Steps:

Step 0
---------- 
Touch the input field for the keyboard to come up

Step 1
---------- 
Type '1'

Step 2
---------- 
Type '2'



Actual results:

Step 1
---------- 
Output:
1. Alert content: '1'
2. Alert content: 'new input'

Step 2
---------
Output:
1. Alert content: 'new' -> I click ok then step 2 appears
2. Alert content: 'new input' -> I click ok then step 3 appears
3. Alert content: 'new inputinput2' -> I click ok then then step 4 appears
4. Alert content: 'new input'

Expected results:

Step 1
---------- 
Output:
1. Alert content: '1'

Step 2
---------
Output:
1. Alert content: 'new input2'

Note: On Chrome this works fine.

Comment 4

[Alex Caziuc]

Tried it on S7 edge(6.0.1) and it's the exact same behaviour as yours.

Comment 5

[Bart]

Thanks, I thought I'm going mad ;)

Comment 6

[Kevin Brosnan [Ex-Mozilla]]

Alex does this reproduce on Nightly/Aurora/Beta?

Comment 7

[Alex Caziuc]

Yes. I tested using Galaxy S7 Edge(6.0.1) on Beta(49.0b11), Aurora - 50.0a2(2016-09-08) and Nightly - 51.0a1(2016-09-08) and it's reproducible as in description.

Comment 8

[James Willcox (:snorp) ([e-mail]) (he/him)]

Jim, maybe we don't expect the value to be changed in the 'input' event?

Comment 9

[(inactive) Jim Chen [:jchen] [:darchons]]

This is actually a behavior of the Samsung keyboard. For predictive input, the Samsung keyboard does not expect the text to change by itself, but when the text does change, the keyboard internally keeps using the previous input. If you turn off "Predictive text" in the Samsung keyboard settings, this behavior goes away.

Also, the same behavior is seen in native Android text fields, so it's not specific to Firefox for Android. Chrome/WebView has a different text input implementation so their behavior is different than the Fennec / native Android behavior.

Based on that, I'm closing this as WONTFIX. What is your use case for modifying the text during an input event? Maybe there is a work around for this situation.

Comment 10

[Bart]

Thanks for looking into this, your findings make perfect sense!

We are actively formatting user input as he/she types - inserting a thousands-separator into the numbers, thus we need to tap into the 'input' event. I've came up with a quick work around that looks for a buggered input and fixes it, seems to be working :)

cheers