Closed
Bug 1170968
Opened 10 years ago
Closed 7 years ago
Can't input text in CNN search bar because it blurs when window is resized, and window is resized when opening on-screen keyboard
Categories
(Web Compatibility :: Site Reports, defect, P5)
Tracking
(tracking-b2g:backlog, b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected, b2g-master affected)
RESOLVED
WONTFIX
| tracking-b2g | backlog |
People
(Reporter: liuke, Unassigned)
References
()
Details
(Whiteboard: [2.2-nexus-5-l] [needscontact] [country-us] [js])
Attachments
(3 files)
[1.Description]:
[Flame v2.2 & v3.0][Nexus 5 v2.2 & v3.0][Browser]The chars can't be input to CNN search bar.
[2.Testing Steps]:
1.Launch Browser.
2.Go to "cnn.com".
3.Tap the CNN search bar, and input chars.
[3.Expected Result]:
3.The chars should be input successfully, and keyboard should display normally.
[4.Actual Result]:
3.The chars can't be input successfully, and the keyboard will hide.
[5.Reproduction build]:
Device: Flame 2.2 version(Affected):
Build ID 20150602162502
Gaia Revision a9aeb08263f1a727136e8ae78425e52431c82770
Gaia Date 2015-06-02 13:04:40
Gecko Revision https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/5b3f1796ddf6
Gecko Version 37.0
Device Name flame
Firmware(Release) 4.4.2
Firmware(Incremental) eng.cltbld.20150602.195401
Firmware Date Tue Jun 2 19:54:11 EDT 2015
Bootloader L1TC000118D0
Device: Flame 3.0 version(Affected):
Build ID 20150602160205
Gaia Revision 6d477a7884273886605049b20f60af5c1583a150
Gaia Date 2015-06-01 16:41:42
Gecko Revision https://hg.mozilla.org/mozilla-central/rev/9eae3880b132
Gecko Version 41.0a1
Device Name flame
Firmware(Release) 4.4.2
Firmware(Incremental) eng.cltbld.20150602.192511
Firmware Date Tue Jun 2 19:25:20 EDT 2015
Bootloader L1TC000118D0
Device: Nexus 5_2.2 version(Affected):
Build ID 20150602162502
Gaia Revision a9aeb08263f1a727136e8ae78425e52431c82770
Gaia Date 2015-06-02 13:04:40
Gecko Revision https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/5b3f1796ddf6
Gecko Version 37.0
Device Name hammerhead
Firmware(Release) 5.1
Firmware(Incremental) eng.cltbld.20150602.193831
Firmware Date Tue Jun 2 19:38:46 EDT 2015
Bootloader HHZ12f
Device: Nexus 5_3.0 version(Affected):
Build ID 20150602160205
Gaia Revision 6d477a7884273886605049b20f60af5c1583a150
Gaia Date 2015-06-01 16:41:42
Gecko Revision https://hg.mozilla.org/mozilla-central/rev/9eae3880b132
Gecko Version 41.0a1
Device Name hammerhead
Firmware(Release) 5.1
Firmware(Incremental) eng.cltbld.20150602.192258
Firmware Date Tue Jun 2 19:23:13 EDT 2015
Bootloader HHZ12f
[6.Reproduction Frequency]:
Always Recurrence,5/5
[7.TCID]:
Free Test
[8.Note]:
Yahoo.com, www.baidu.com, tw.yahoo.com... input chars normally in search bar.
| Reporter | ||
Updated•10 years ago
|
status-b2g-v2.2:
--- → affected
status-b2g-master:
--- → affected
| Reporter | ||
Comment 1•10 years ago
|
||
Comment 2•10 years ago
|
||
Can we see if this happens in an earlier 2.2 build and if so get a regression window?
Keywords: qaurgent,
regressionwindow-wanted
Updated•10 years ago
|
blocking-b2g: --- → 2.2+
Comment 3•10 years ago
|
||
Able to reproduce this issue. Finding the regression window now.
Device: Flame 2.2
BuildID: 20150531042140
Gaia: b4582cc394e0919623263997c0cdb0b4751a1403
Gecko: 78d8b0a4303d
Version: 37.0 (2.2)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
QA Contact: jmercado
Comment 4•10 years ago
|
||
This issue occurs on 2.1, 2.0 and the V18D-1 Flame KK base image so it doesn't seem to be a regression or at least one caused by changes at the site that interacts oddly with our browser.
Environmental Variables:
Device: Flame 2.1
BuildID: 20150602075614
Gaia: 2304a1f6327c2ccf35d6995ee16f2231ed1f22a3
Gecko: e08cbbf120f1
Version: 34.0 (2.1)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Environmental Variables:
Device: Flame 2.0
BuildID: 20150602080014
Gaia: 5552bf529d3d6775a968942e9afa6c1d4037362c
Gecko: 26bc2c071c94\
Version: 32.0 (2.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: qaurgent,
regressionwindow-wanted
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
status-b2g-v2.0:
--- → affected
status-b2g-v2.1:
--- → affected
Flags: needinfo?(ktucker)
Comment 6•10 years ago
|
||
Quick update. In my test, the keyboard would quickly close and I have no enough time to input any characters. I think it is because of different memory setting.
In my logcat, I got below error from [1]
'I/Gecko ( 209): -*- SettingsRequestManager: No keys to change entered!'
[1] https://github.com/mozilla/gecko-dev/blob/master/dom/settings/SettingsRequestManager.jsm#L448
Flags: needinfo?(hcheng)
Comment 7•10 years ago
|
||
NI keyboard developer owner. Tim, could you help here?
Flags: needinfo?(timdream)
Updated•10 years ago
|
Assignee: nobody → timdream
Status: NEW → ASSIGNED
Flags: needinfo?(timdream)
Comment 8•10 years ago
|
||
This should be a compatibility issue on CNN.com itself. Open the Web Console and type |window.onresize.toString()| I see the following function:
function (){
"use strict";
jQuery("html").is(".iemobile, .android, .ios")||window.CNN.navigation.$search.blur()}
On our phone |jQuery("html").is(".iemobile, .android, .ios")| evaluates to |false| which contributes to the root cause:
1. When we tap on the search input, the search input receives focus and the keyboard rises.
2. When keyboard animation finishes, we resize the frame containing the page and triggers the resize event.
3. When the resize event triggers the above function will blur the input.
I don't know why such code needs to exist in any platform.
Interestingly, iOS Safari doesn't actually trigger the onresize function when it's keyboard show up. I think they might have implemented some kind of viewport rules like bug 970093.
Anyhow, we need them to get this fixed.
(BTW Modernizr on the site set us as the following in the className in <html>: "js touch geolocation websockets textshadow csscolumns csstransforms3d fontface localstorage webworkers no-ios no-android no-iemobile flexbox no-ie8 mobile phone no-tablet mobilegradea")
Assignee: timdream → nobody
Status: ASSIGNED → NEW
blocking-b2g: 2.2+ → 2.2?
Component: Gaia::Browser → Mobile
Product: Firefox OS → Tech Evangelism
Comment 9•10 years ago
|
||
It would be safer not to trigger onresize when the on-screen keyboard opens - this is *not* the only site with such problems.
Summary: [Browser]The chars can't be input to CNN search bar. → Can't input text in CNN search bar because it blurs when window is resized, and window is resized when opening on-screen keyboard
Whiteboard: [2.2-nexus-5-l] → [2.2-nexus-5-l] [needscontact] [country-us] [js]
Comment 10•10 years ago
|
||
Is Fx Android also affected? (I don't know which flag to set to get this question answered)
Comment 11•10 years ago
|
||
Nah, search works as expected in Fennec.
Comment 12•10 years ago
|
||
(In reply to Mike Taylor [:miketaylr] from comment #11)
> Nah, search works as expected in Fennec.
Right, Fennec runs on Android ...
Comment 13•10 years ago
|
||
(In reply to Tim Guan-tin Chien [:timdream] (slow response; please ni? to queue) from comment #12)
> (In reply to Mike Taylor [:miketaylr] from comment #11)
> > Nah, search works as expected in Fennec.
>
> Right, Fennec runs on Android ...
So what question are you actually asking?
If it's:
> Is Fx Android also affected?
No. See Comment #11.
Comment 14•10 years ago
|
||
(In reply to Mike Taylor [:miketaylr] from comment #13)
Nah, just saying I realized Fennec runs on Android, so comment 8 will evaluate to true, right after I ask the question in comment 10.
Flags: needinfo?(timdream)
Comment 15•10 years ago
|
||
[Blocking Requested - why for this release]:
Continue fixing on next release
blocking-b2g: 2.2? → 2.5?
Updated•10 years ago
|
blocking-b2g: 2.5? → 2.5+
Comment 16•10 years ago
|
||
We can't block on evangelism bug, it's outside of our control. Unless there is a policy say we should...
Flags: needinfo?(mpotharaju)
Comment 17•10 years ago
|
||
| contact email | ||
First attempt at Contacting someone at CNN.
And agreed to not block a release on evangelism bug outside of Mozilla community control.
We may fix things on our side, but that's different and not anymore an evangelism bug.
Whiteboard: [2.2-nexus-5-l] [needscontact] [country-us] [js] → [2.2-nexus-5-l] [sitewait] [country-us] [js]
Comment 18•10 years ago
|
||
[Tracking Requested - why for this release]:
Thanks for the insight Tim. Missed this was an Evangelism issue. Agreed. Removing nomination and blocker for 2.5. Pushing it to backlog.
blocking-b2g: 2.5+ → ---
tracking-b2g:
--- → backlog
Updated•10 years ago
|
Flags: needinfo?(mpotharaju)
Comment 19•10 years ago
|
||
Switching back to needscontact. Hunt for a contact restarts.
The email came back with an error. The person has left.
Whiteboard: [2.2-nexus-5-l] [sitewait] [country-us] [js] → [2.2-nexus-5-l] [needscontact] [country-us] [js]
Comment 20•10 years ago
|
||
| contact form | ||
CNN/Turner has a tool page
http://edition.cnn.com/tools/index.html
They also have a feedback. I'm usually not confident about it, but let's try.
http://edition.cnn.com/feedback
I sent the feedback which has basically no expectations of answers. :/
Updated•10 years ago
|
QA Contact: jmercado → kdubost
Updated•10 years ago
|
Assignee: nobody → kdubost
Status: NEW → ASSIGNED
Updated•10 years ago
|
QA Contact: kdubost
Updated•9 years ago
|
Priority: -- → P5
Comment 21•7 years ago
|
||
The Firefox OS project is not active anymore.
Assignee: kdubost → nobody
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
| Assignee | ||
Updated•6 years ago
|
Product: Tech Evangelism → Web Compatibility
| Assignee | ||
Updated•1 year ago
|
Component: Mobile → Site Reports
You need to log in
before you can comment on or make changes to this bug.
Description
•