Closed Bug 1533665 Opened 5 years ago Closed 4 years ago

Search bar popup doesn't open while write something in the search bar


(Firefox :: Search, defect)

66 Branch
Not set





(Reporter: maruf.rahman.95, Unassigned)


(Keywords: regression)


(1 file)

Attached image bug.gif

Build Id: 20190307095232
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0
Operating System: Windows 7, 64 Bit!

Steps to Reproduce:

  1. Open Firefox Beta 66.0b14 with a new profile
  2. Go to about:preferences#search
  3. Enable the "Add search bar in toolbar" option
  4. Go to ta new tab and click on the 'search icon' of the search bar. You will see a pop-up with search engine list
  5. Close the pop-up
  6. Now, write something in the search bar, e.g: football
  7. Click on somewhere in the tab to remove the focus from the search bar
  8. Now repeat step 4 means click on the 'search icon' again to see the pop-up

Actual Result:
The pp-up is broken. Only white shape of the pop-up opens. Nothing is there(see the attached GIF)

Expected Result:
The pop-up with search engine list should open without any problem

Has STR: --- → yes
QA Whiteboard: [testday-20190308]

Hi Mohammad, thanks for filing! Do you see any Javascript errors in the browser console? You can find it in 'Tools' > 'Web Developer' > 'Browser Console'.

Flags: needinfo?(maruf.rahman.95)

I have tried to generate error messsages with different serach enginers and I have found the following result:


  1. SearchSuggestionController: HTTP Timeout SearchSuggestionController.jsm:380

  2. Error logged with the Track&Report JS errors API(http://tiny/1covqr6l8/wamazindeClieUserJava): {"m":"Ad Feedback API response was invalid.","csm":"v5 ueLogError callee","logLevel":"ERROR","attribution":"SearchAssets:100b9977e4f43a1f9559ec91432f7ae0550a8e6a","pageURL":"","s":["function(){if(g.ue_err.erl){var b=g.ue_err.erl.length,l,a;for(l=0;l<b;l++)a=g.ue_err.erl[l],B(a.ex,;ue_err.erl=[]}}","function(g,f){function y(b){if(b)return b.replace(/^\s+|\s+$/g,"")}function w(b,l){if(!b)return{};var a="INFO"===l.logLevel;b.m&&b.m.message&&(b=b.m);var e=l.m||l.message||"",e=b.m&&b.m.message?e+b.m.message:b.m&&"Error handler invoked by "" tag"):b.m?e+b.m:b.message?e+b.message:e+"Unknown error",e={m:e,,type:b.type,csm:N+" "+(b.fromOnError?"onerror":"ueLogError")},k,f,h=0,q;e.logLevel=l.logLevel||A;l.adb&&(e.adb=l.adb);if(k=l.attribution)"],"t":4419} <unavailable> ClientSideMetricsAUIJavascript@jserrorsForester.10f2559e93ec589d92509318a7e2acbac74c343a.V2.js:4:346

  3. The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature. rb

  4. Error while calling actor 'parentProcessTarget's method 'ensureCSSErrorReportingEnabled' Argument 1 of InspectorUtils.getAllStyleSheets is not an object. protocol.js:1048:5

  5. stylesheets actor: fetch failed for data:text/css,, using system principal instead. stylesheets.js:213:5

  6. uncaught exception: Protocol error (unknownError): Argument 1 of InspectorUtils.getAllStyleSheets is not an object.

  7. ensureCSSErrorReportingEnabled@resource://devtools/server/actors/targets/browsing-context.js:1003:9


  1. Use of Mutation Events is deprecated. Use MutationObserver instead. ee8d79e1.js:1:1409

  2. An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can remove its sandboxing. search

  3. The character encoding of a framed document was not declared. The document may appear different if viewed without the document framing it. nosignin

  4. The script from “” was loaded even though its MIME type (“text/html”) is not a valid JavaScript MIME type.[Learn More] search

Flags: needinfo?(maruf.rahman.95)

Thank you logging this issue, Mohammad!

Unfortunately I could not reproduce this issue on any of our machines. Can you please assist us with an regression window?

In order to find it easier we suggest to use our mozregression tool.

Link to mozregression:

Flags: needinfo?(maruf.rahman.95)

Thank you, Mohammad! Awesome job and fast time reply.

So we would need more information to debug this, the pushlog is too large to narrow it down.

Closing as invalid, suspect with no other reports that this issue was a graphics issue that didnt persist. If you can still reproduce please reopen with more information and ideally steps to reproduce

Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.