Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Ovo će web mjesto raditi na ograničen način, dok obavljamo održavanje stranice. Ako neki članak ne riješi tvoj problem i ako želiš postaviti pitanje, naša zajednica za podršku spremna je pomoći na Twitteru @FirefoxSupport i na Redditu /r/firefox.

Avatar for Username

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Ova tema je arhivirana. Postavi novo pitanje ako trebaš pomoć.

Weird problem: 'Search in page' (CTRL+F) orks fine on most pages but is not working on one particular page

  • 1 odgovor
  • 1 ima ovaj problem
  • 17 prikaza
  • Posljednji odgovor od micdal22

micdal22
micdal22
more options

The page search facility (Ctrl+F) works fine for most pages, but doesn't work on one particular page.

The page in question happens to be my home page and is one that I created via Macromedia Dreamweaver. It is my web portal containing numerous links (to all the sites I usually access).

I press Ctrl+F and the search box appears at bottom of screen, as usual. I enter a word in the search box, click the up and down arrows, but it doesn't find any matches, even though that word definitely exists on the page (multiple times). (The Highlight All, Match Case, Whole Words options are not selected). If I enable "Highlight All", nothing is highlighted.

This problem has surfaced in the last month or so. I suspect it may have crept in with a recent Firefox update, as this wasn't a problem in the past. My setup: Desktop PC, Win 10 (64bit), Firefox is 82.0 (64-bit) -the current version, and I'm using the Default Theme.

PS: I opened the same page with Microsoft Edge and the Page Search works fine there. .... but Firefox is my preferred browser, so I need to get to the bottom of this problem.

Any suggestions on how I can resolve this weird problem?

The page search facility (Ctrl+F) works fine for most pages, but doesn't work on one particular page. The page in question happens to be my home page and is one that I created via Macromedia Dreamweaver. It is my web portal containing numerous links (to all the sites I usually access). I press Ctrl+F and the search box appears at bottom of screen, as usual. I enter a word in the search box, click the up and down arrows, but it doesn't find any matches, even though that word definitely exists on the page (multiple times). (The Highlight All, Match Case, Whole Words options are not selected). If I enable "Highlight All", nothing is highlighted. This problem has surfaced in the last month or so. I suspect it may have crept in with a recent Firefox update, as this wasn't a problem in the past. My setup: Desktop PC, Win 10 (64bit), Firefox is 82.0 (64-bit) -the current version, and I'm using the Default Theme. PS: I opened the same page with Microsoft Edge and the Page Search works fine there. .... but Firefox is my preferred browser, so I need to get to the bottom of this problem. Any suggestions on how I can resolve this weird problem?

Izabrano rješenje

Problem SOLVED. I opened the file with Dreamweaver, changed a few characters and then saved it.

That's all I did but now the search facility (Ctrl+F) works fine once again.

As most of us would know, sometimes weird things happen with computers and this one fits into that category. I can't fully explain the behavior, but I'm glad things are working again.

Pročitaj ovaj odgovor u kontekstu 👍 0

Svi odgovori (1)

micdal22
micdal22 Vlasnik pitanja
more options

Odabrano rješenje

Problem SOLVED. I opened the file with Dreamweaver, changed a few characters and then saved it.

That's all I did but now the search facility (Ctrl+F) works fine once again.

As most of us would know, sometimes weird things happen with computers and this one fits into that category. I can't fully explain the behavior, but I'm glad things are working again.