Closed
Bug 942845
Opened 11 years ago
Closed 11 years ago
Results refresh twice after pressing enter on the keyboard
Categories
(Firefox OS Graveyard :: Gaia::Everything.me, defect)
Tracking
(blocking-b2g:1.3+)
RESOLVED
FIXED
blocking-b2g | 1.3+ |
People
(Reporter: zcampbell, Assigned: ranbena)
References
Details
(Keywords: regression, Whiteboard: [fromAutomation][systemsfe])
Attachments
(3 files, 2 obsolete files)
STR
1. Tap in e.me search panel
2. Type in 'twitter'
3. Tap enter key, observe the results load
4. Wait 2-3 seconds
5. results will clear and re-load again
Device Hamachi
Gecko http://hg.mozilla.org/mozilla-central/rev/250bb14d76d4
Gaia 9935ceb4fe96fff48e78b941cfd2a69d8639a418
BuildID 20131125040208
Version 28.0a1
Comment 1•11 years ago
|
||
Ran - Why are we double refreshing here?
Seems like this is a recent regression too.
Flags: needinfo?(ran)
Keywords: regression,
regressionwindow-wanted
Reporter | ||
Comment 2•11 years ago
|
||
Judging from the automation results the *last passing* build was:
Gaia: 13687c598c3b5ef4cff9eef8d0ed3bb57c5f9d65
Gecko: http://hg.mozilla.org/mozilla-central/rev/dbf94e314cde
BuildID 20131122040202
Version 28.0a1
Updated•11 years ago
|
Keywords: regressionwindow-wanted
Comment 3•11 years ago
|
||
Actually, let me leave regression window wanted here.
Can we get the regression window down to a day? That will pin point the regressing commit more directly.
Keywords: regressionwindow-wanted
Comment 4•11 years ago
|
||
If it's regressed by a commit on the client-side, then bug 925970 is likely the candidate for causing this.
Updated•11 years ago
|
QA Contact: jzimbrick
Comment 5•11 years ago
|
||
Regression Window:
Last Working Environmental Variables:
Device: Buri v1.3 Mozilla RIL
BuildID: 20131121040202
Gaia: 71063dd91bc8cbb15ba335236ed67a1c5058bd58
Gecko: cf378dddfac8
Version: 28.0a1
Base Image: V1.2_20131115
First Broken Environmental Variables:
Environmental Variables:
Device: Buri v1.3 Mozilla RIL
BuildID: 20131122040202
Gaia: 13687c598c3b5ef4cff9eef8d0ed3bb57c5f9d65
Gecko: dbf94e314cde
Version: 28.0a1
Base Image: V1.2_20131115
Keywords: regressionwindow-wanted
Comment 6•11 years ago
|
||
I'm unsure the above regression window is right - Zac's results say that this was working on the 11/22 build. This needs to be double checked.
Keywords: regressionwindow-wanted
Comment 7•11 years ago
|
||
Yes, it appears the variables posted above were incorrect. This should be the correct variables, after making an everything.me search on the 20131122123502 build, the search will run again after a few seconds and the results list repopulates.
Regression Window:
Working:
Device: Buri v1.3 Mozilla RIL
BuildID: 20131122040202
Gaia: 13687c598c3b5ef4cff9eef8d0ed3bb57c5f9d65
Gecko: dbf94e314cde
Version: 28.0a1
Base Image: V1.2_20131115
Broken:
Environmental Variables:
Device: Buri v1.3 Mozilla RIL
BuildID: 20131122123502
Gaia: 2cc78d696482e0434b584f5645af55e3105e59a2
Gecko: 3c4fc4279e6a
Version: 28.0a1
Base Image: V1.2_20131115
Keywords: regressionwindow-wanted
Comment 8•11 years ago
|
||
Okay, then this is definitely caused by the landing in bug 925970.
Switching needinfo on aus to weigh in on why the double refresh is happening.
Nominating because we're wasting network resources here, which is costly to a user if they are on a data connection.
blocking-b2g: --- → 1.3?
Flags: needinfo?(ran) → needinfo?(aus)
Whiteboard: [fromAutomation] → [fromAutomation][systemsfe]
Comment 9•11 years ago
|
||
Talked with aus in IRC - sounds like it seems odd this is happening by bug 925970, as most of the changes there were CSS based.
Flags: needinfo?(aus)
Assignee | ||
Comment 10•11 years ago
|
||
Bug 935845 might be the cause. Checking it out.
Assignee | ||
Comment 11•11 years ago
|
||
The bug originated in Bug 935845 as clicking the "return" button doesn't clear the 'idle' and 'pause' timeouts (which trigger a search for the exact search term).
Attachment #8338337 -
Flags: review?(evyatar)
Attachment #8338337 -
Flags: review?(crdlc)
Comment 12•11 years ago
|
||
Comment on attachment 8338337 [details]
Patch - redirect to github PR
perfect
Attachment #8338337 -
Flags: review?(evyatar) → review+
Comment 13•11 years ago
|
||
Comment on attachment 8338337 [details]
Patch - redirect to github PR
10x Ran
Attachment #8338337 -
Flags: review?(crdlc) → review+
Assignee | ||
Comment 14•11 years ago
|
||
Landed on master
https://github.com/mozilla-b2g/gaia/commit/ffb42451ca87be367df9127240a151c2b3acec54
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Updated•11 years ago
|
blocking-b2g: 1.3? → 1.3+
Reporter | ||
Comment 15•11 years ago
|
||
(In reply to Ran Ben Aharon (Everything.me) from comment #14)
> Landed on master
> https://github.com/mozilla-b2g/gaia/commit/
> ffb42451ca87be367df9127240a151c2b3acec54
I'm sorry but it's still replicating on today's builds. It definitely includes your commit, I double checked it.
Which device did you test it on? I'm using a Hamachi.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 16•11 years ago
|
||
Tested on Unagi. Can you re-test? :/
Reporter | ||
Comment 17•11 years ago
|
||
Sorry, same again today..
Reporter | ||
Comment 18•11 years ago
|
||
Reporter | ||
Comment 19•11 years ago
|
||
Reporter | ||
Comment 20•11 years ago
|
||
Attachment #8339398 -
Attachment is obsolete: true
Assignee | ||
Comment 21•11 years ago
|
||
Zac, thanks for hanging in there :)
I've found it was a mistake I made in the original patch.
I'll back out the patch as soon as Gaia reopens and re-PR it with the fix.
Assignee | ||
Comment 22•11 years ago
|
||
Backed out the commit
https://github.com/mozilla-b2g/gaia/commit/45cbe2be45c1653765e23c4c1e4aea8ae7e41b8d
Assignee | ||
Comment 23•11 years ago
|
||
Same patch as before but with the small fix
Attachment #8338337 -
Attachment is obsolete: true
Attachment #8339960 -
Flags: review?(evyatar)
Updated•11 years ago
|
Attachment #8339960 -
Flags: review?(evyatar) → review+
Assignee | ||
Comment 24•11 years ago
|
||
Landed on master
https://github.com/mozilla-b2g/gaia/commit/43c37ef8e3f0cca203b1f151cd49e72ccffd8d07
This time for real realz
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Assignee: nobody → ran
You need to log in
before you can comment on or make changes to this bug.
Description
•