This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. اگر به کمک نیاز دارید لطفاً یک سؤال بپرسید.

PDF.js failed to reopen search bar using Ctrl-F after switching away and back

  • 3 پاسخ
  • 1 has this problem
  • 1 view
  • آخرین پاسخ توسّط philipp

outloudvi
outloudvi
more options

Firefox 63.0b9, 64 bit, Developer version. Reproduceable for several times.

Steps to reproduce:

  • Open a pdf in Firefox
  • Ctrl-F and search something (not required to hit any result)
  • Close the search box
  • Switch to another tab, do some scrolling
  • Switch back
  • Ctrl-F doesn't call out the search box
Firefox 63.0b9, 64 bit, Developer version. Reproduceable for several times. Steps to reproduce: * Open a pdf in Firefox * Ctrl-F and search something (not required to hit any result) * Close the search box * Switch to another tab, do some scrolling * Switch back * Ctrl-F doesn't call out the search box

Chosen solution

hi outloudvi, thanks for testing our beta builds and reporting the issue.

we had a similar bug for this already on file at https://bugzilla.mozilla.org/show_bug.cgi?id=1486984 where i've added your reproducible steps as further information.

Read this answer in context 👍 1

All Replies (3)

philipp
philipp
  • Moderator
more options

Chosen Solution

hi outloudvi, thanks for testing our beta builds and reporting the issue.

we had a similar bug for this already on file at https://bugzilla.mozilla.org/show_bug.cgi?id=1486984 where i've added your reproducible steps as further information.

outloudvi
outloudvi Question owner
more options

This seems to be fixed when testing in Firefox 63.0b14. Thanks!

philipp
philipp
  • Moderator
more options

thank you for coming up with these easy reproducible steps!