The Find on Page problem was supposed to be fixed in v61. I'm on v62, and issue still exists. Search doesn't work on embedded page content still. Sad. :(
Saw in an answer to a question posted 4 months ago that the issue with not being able to use Find On Page to search for words inside embedded content (like in WordPress CSS) was going to be solved in v61. I'm in v62 and it still doesn't work.
For example, if I do a search on the term "widget" in a the style.css of a page, it gives me 0 results, but if scroll down a little bit, I can clearly see the word "widget" in the content. With it visible on the page, if I then do a Find On Page search for "widget", it gives me 1 result - the one I manually found. As I scroll down the page, I can see a dozen more uses of the word "widget", but they only show up in the Find On Page results if they are actually visible in the browser window.
Find On Page needs to search ALL of the page content, not just what is VISIBLE in the live browser area.
This used to work just fine, but in the last few versions it doesn't. Can you not fix this already?
所有回复 (6)
SMCunningham said
For example, if I do a search on the term "widget" in a the style.css of a page, it gives me 0 results, but if scroll down a little bit, I can clearly see the word "widget" in the content. With it visible on the page, if I then do a Find On Page search for "widget", it gives me 1 result - the one I manually found. As I scroll down the page, I can see a dozen more uses of the word "widget", but they only show up in the Find On Page results if they are actually visible in the browser window.
Do you mean in /wp-admin/theme-editor.php ?
Yes, I see the same issue there.
When I create a page with one of those CSS files but no fancy editor layout, Find works normally:
https://www.jeffersonscher.com/temp/scrollingdiv.html
So something above having it laid out in that special way seems to be confusing the Find function.
Curiously, if I click in the editor and press Ctrl+f, WordPress displays its own find bar for searching within the code. I don't know whether that is a factor in why Firefox's search doesn't work in there.
Yes. You are correct. That is exactly what I mean.
I understand what you are saying, but Firefox's Find on Page used to be able to find everything in embedded content, like inside the css editor. It no longer does. That seems like the development went backwards for some reason.
Again, I saw a related question posted in your forum 4 months ago, and one of your team members told that guy it would be resolved in v61, but it clearly wasn't.
Examples like the one I created yesterday were fixed. Someone needs to figure out the difference and file a new bug for it.
So...who actually does that? You?
Somehow, I doubt it.
I've never understood exactly what the value was of submitting a tech question to be answered by someone who isn't employed by Mozilla with no means of actually resolving it.
No offense, but opinions by non-employees do not equal answers provided by employees with the power to make software changes. Until there is someway to get this answered directly by someone with authority, I guess I'm just wasting my time here.
Here in support we work with the Firefox we have today: features, settings and workarounds. Support volunteers can sometimes spot the code developers need to fix, but usually not. We can help reach a shared understanding of the problem.
To report a bug to the developers, there is a bug tracking system:
You can post a link to the bug back here for reference.
Here's another example of a code editor (Ace, I think) where Firefox's Find feature doesn't work beyond the visible lines:
https://www.reddit.com/r/firefox/comments/9ongz4/findbar_does_not_work_in_the_cpanel_file_manager/
Fortunately, Ace has a built-in Find bar (it intercepts Ctrl+f).