1332908 - Unable to search through about:home in responsive design mode

Status: RESOLVED INVALID

(DevTools :: Responsive Design Mode, defect, P3)

Description

[sakshiprajapati000]

Attachment: CaptureRDM_LI.jpg

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:51.0) Gecko/20100101 Firefox/51.0
Build ID: 20170116133120

Steps to reproduce:

Step 1 -Launch Firefox.	
Step 2 -Enable RDM tool.  	
Step 3 -Navigate to a remote page. (Eg. www.wikipedia.org)	with the welcome page search box of firefox (i.e. "->" arrow) rather than Address bar.



Actual results:

While trying to search through the welcome screen search box of firefox(i.e. "->" arrow) in Responsive Design Mode , The search bar doesn't work.
No action.



Expected results:

successfully launch the website or search results.

Comment 1

[YF (Yang)]

WFM in Fx51.0 & 52.0a2 (2017-01-22) on Win10.


Can you check your Browser Console (not Web Console) when the problem occurred? There may be some errors thrown.

Comment 2

[Loic]

I can reproduce it with the new RDM.

STR:
1) Open about:home
2) Switch to RDM
3) Type any keyword into the search bar

Result: search suggestions are not displayed (no dropdown list), search button doesn't work.

Comment 3

[Loic]

I tested with old nightlies, the issue is here since the launch of the new RDM (bug 1296498).

Comment 4

[Loic]

More details:

1) For each letter typed in the search bar of about:home, this error is sent:

aWindow is null PrivateBrowsingUtils.jsm:48
	pbu_privacyContextFromWindow resource://gre/modules/PrivateBrowsingUtils.jsm:48:5
	isBrowserPrivate resource://gre/modules/PrivateBrowsingUtils.jsm:44:12
	this.ContentSearch.getSuggestions< resource://app/modules/ContentSearch.jsm:272:16
	next self-hosted:1119:9
	TaskImpl_run resource://gre/modules/Task.jsm:319:42
	TaskImpl resource://gre/modules/Task.jsm:277:3
	asyncFunction resource://gre/modules/Task.jsm:252:14
	this.ContentSearch._onMessageGetSuggestions< resource://app/modules/ContentSearch.jsm:432:29
	next self-hosted:1119:9
	TaskImpl_run resource://gre/modules/Task.jsm:319:42
	TaskImpl resource://gre/modules/Task.jsm:277:3
	asyncFunction resource://gre/modules/Task.jsm:252:14
	this.ContentSearch._onMessage< resource://app/modules/ContentSearch.jsm:396:13
	next self-hosted:1119:9
	TaskImpl_run resource://gre/modules/Task.jsm:319:42
	bound TaskImpl_run self-hosted:956:17
	process resource://gre/modules/Promise-backend.js:917:23
	walkerLoop resource://gre/modules/Promise-backend.js:801:7
	bound walkerLoop self-hosted:912:17
	bound bound walkerLoop self-hosted:912:17

2) When clicking on the search button, this error is sent:

browser.loadURIWithFlags is not a function ContentSearch.jsm:247
	performSearch resource://app/modules/ContentSearch.jsm:247:7
	_onMessageSearch resource://app/modules/ContentSearch.jsm:414:5
	this.ContentSearch._onMessage< resource://app/modules/ContentSearch.jsm:396:13
	InterpretGeneratorResume self-hosted:1212:8
	next self-hosted:1119:9
	TaskImpl_run resource://gre/modules/Task.jsm:319:42
	bound TaskImpl_run self-hosted:956:17
	process resource://gre/modules/Promise-backend.js:917:23
	walkerLoop resource://gre/modules/Promise-backend.js:801:7
	bound walkerLoop self-hosted:912:17
	bound bound walkerLoop self-hosted:912:17

Comment 5

[Julien Cristau [:jcristau]]

Tracking new RDM issue for 52/53

Comment 6

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

[Tracking Requested - why for this release]:

Thanks for filing!

My initial reaction is that this is pretty low priority, since I would imagine most RDM users will open RDM from a content page instead of about:home.

If we learn that many people are affected by this issue, we can reevaluate.

Since it seems low priority, I'm clearing the regression tracking and tracking flags.

Comment 7

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

(Ignore the "[Tracking Requested - why for this release]:" in the previous comment.)

Comment 8

[Julien Cristau [:jcristau]]

Mass wontfix for bugs affecting firefox 52.

Comment 9

[Martin Balfanz [:mbalfanz]]

As described in bug 1492363 we don't display the what's new page anymore inside RDM. So I think we can close it as invalid. Feel free to reopen the bug if I'm missing something :)