Removed from firefox.htm on Firefox 1.5 now that Fx2 is out 1 month Webpage as the 7th (last) tab (have had many more tabs open earlier, perhaps 22). Possible examples: - can't find "NOWRAP", Can't fine "FOLD" with this.Important: the only accessibility options showing up as User set for me in 1.5.01 on are now:Īccessibility.accesskeycausesactivation, user set, boolean, falseĪccessibility.typeaheadfindflashBar, user set, integer, 0īypass in bug 175620 suggests opening a new window (Ctrl+N), typing in some text then closing it. Find is still unreliable but it usually works almost always fails now in 1.5.0.1 getting worse by the week Possible soution: accessibility.typeaheadfind has now been reset to false (default). May also be messing with your options (fixing after Firefox messed up). Inside Firefox in second, then both fail.įind not functioning and Space Bar not acting like Page Down cropped upĪgain - Fixed(almost): keep an eye on your options, though some extensions See if this fails (my home page in first tab, and Make sure you have your options set correctly or In Firefox 1.5.0.1 the PageUp and PagedDown keys also frequently. Not be in an input areas including Search (engines), and Find. Use the Esc key from Find to restore space bar scrolling down, as you must Major cause of problem is the Find, if you terminate find with the red close icon you can use page down but not the spacebar. Word Count) will restore this ability and left click anywhere
Space Bar not working like Page Down key.
As the problem comes and goes a couple of hours is was hardly a valid timeframe for checking. “Phrase not found after attempting a FIND simply cannot be trusted as being true, and you will have to double-check with a non Firefox text editor or another browser.Ĭould be the AutoTOC GreaseMonkey script, which I have now disabled (), the start of the problem was probably about July 2005 when the script became availble. Added bonusīoth Highlight and Find work at same time. Turn off "Find as you Type" in accessibility option. I think the Firefox developers must use "/" to start a Find rather than Ctr+F as that seems to work better - how else could Firefox be released with a broken Find - turns out to be just something else to try, it fails just as inconsistently.įIND working correctly now with 1.5.0.1 Still Broken, worse every week, Highlight probably always works but it is like looking for pine needles on a tennis court. Page Actually it works for cookies, try another word, it is very sporaic when it does work. try to find cookies whichĬan be found if you use \cookies at this other Find does not always work (#problemwithfind), i.e.The other option, “ Allow text to be selected with the keyboard” (formerly Move system caret with focus/selection), as you would lose the ability to page down After Firefox updates Make sure you have unchecked Begin finding when you begin typing (formerly Find As You Type) under Options, Advanced, General(tab), Accessibility as Find will work better and would probably allow use of single key shortcuts in Context Menu Extensions]. There is still no provision for find whole word(s) but theĪddition of Match case brings it pretty much inline with Find Use ' to find link text or / to find text. Is that you can use the Esc key to remove the Find toolbarīefore leaving it as opposed to having to click on the toĬlose the find toolbar. Though I don't see it documented the important part I was missing Obscuring what you are looking for I actually like it. It will never put the dialog in the middle of the screen Even in 1.5.0.4 Find does not always work so isįind in Firefox (#find) Ok in 1.5.0.2 (but did fail after checking for updates/update worked again once restarted)Ī change that I really disliked that was introduced in Firefoxġ.0PR was the change to Find (Ctrl+F) that puts a find
Problem: Firefox FIND still not working consistently even in 1.5.0.4įind appears to be working a bit better in 1.5.0.2 so have removed the following content from