Closed
Bug 1102934
Opened 11 years ago
Closed 4 years ago
No neterror page or any feedback displayed if a search request times out
Categories
(Firefox :: Search, defect, P5)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: FlorinMezei, Unassigned)
Details
(Whiteboard: [fxsearch])
Reproducible with Firefox 34 Beta 11 - BuildID: 20141120192249
Environment: Windows 7 x64, Windows 8 x86, Ubuntu 12.04 x86, Mac OS X 10.9.5
Steps to reproduce:
1. Open Firefox and open a new tab.
2. Set an offline search engine as default (did this while the Yahoo service was down... not sure how to reproduce this situation).
3. Type in a search term in the search bar and press enter.
Expected results:
The user should see the "Connecting" spinner in the tab, and then an error displayed on the page.
Actual results:
The user sees the "Connecting" spinner in the tab, but then the New Tab page remains displayed, without any error or feedback to the user that the search timed out.
Note that in this case, SearchSuggestionController.jsm throws an error in the Browser Console. See http://pastebin.mozilla.org/7435260.
Comment 1•11 years ago
|
||
Are you sure this is related to the new search UI? I don't see how it could possible be related. The SearchSuggestionController error should not be related.
Comment 2•11 years ago
|
||
[Tracking Requested - why for this release]: Affects 34, though it may not be related to the new UI changes. We may be uncovering new issues because of focusing on this area for testing for beta 11, though.
status-firefox34:
--- → affected
tracking-firefox34:
--- → ?
Comment 3•11 years ago
|
||
(In reply to Florin Mezei, QA (:FlorinMezei) from comment #0)
> Note that in this case, SearchSuggestionController.jsm throws an error in
> the Browser Console. See http://pastebin.mozilla.org/7435260.
The pastebin is only one line long, pasting it here to save future readers a click:
SearchSuggestionController: HTTP Timeout in SearchSuggestionController.jsm:331
Comment 4•11 years ago
|
||
After reviewing with Gavin, this is wontfix for 34. I have tracked for 35+. Note that this may not require tracking if this is a relatively old issue.
status-firefox33:
--- → ?
status-firefox35:
--- → affected
status-firefox36:
--- → affected
status-firefox37:
--- → affected
status-firefox-esr31:
--- → ?
tracking-firefox35:
--- → +
tracking-firefox36:
--- → +
tracking-firefox37:
--- → +
Flags: firefox-backlog?
Comment 5•10 years ago
|
||
I think this is not a regression. Can this even be reproduce consistently?
No longer blocks: fx34-searchui
status-firefox33:
? → ---
status-firefox34:
wontfix → ---
status-firefox35:
affected → ---
status-firefox36:
affected → ---
status-firefox37:
affected → ---
status-firefox-esr31:
? → ---
tracking-firefox34:
+ → ---
tracking-firefox35:
+ → ---
tracking-firefox36:
+ → ---
tracking-firefox37:
+ → ---
Flags: firefox-backlog? → firefox-backlog-
Updated•10 years ago
|
Priority: -- → P5
Whiteboard: [fxsearch]
Updated•10 years ago
|
Rank: 55
Updated•10 years ago
|
Rank: 55 → 65
Comment 6•4 years ago
|
||
I've tried this on the latest nightly both the new tab page and search bar work fine in this scenario.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•