Users and developers helping users with generic and technical Pale Moon issues on all operating systems.
Moderator: trava90
Forum rules
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
-
coffeebreak
- Moon Magic practitioner
- Posts: 2986
- Joined: 2015-09-26, 04:51
- Location: U.S.
Unread post
by coffeebreak » 2017-07-07, 05:12
Check that these two preferencess, which are new since PM 27.3, are set to false (default) in about:config.
Code: Select all
accessibility.typeaheadfind.highlightallbydefault
accessibility.typeaheadfind.highlightallremember
(See
Release Notes for PM 27.3)
EDIT: OOPS! I take it back! I didn't catch that you're using PM 27.2.1 - before these prefs were present. XD
Last edited by
coffeebreak on 2017-07-07, 05:34, edited 1 time in total.
-
GMforker
Unread post
by GMforker » 2017-07-07, 05:26
tommy_k wrote:this wasn't a problem with 25.x but now using 27.2.1 I can't find an option to turn off the annoying auto highlight when clicking in search box. about:config has "browser.urlbar.clickselectsall" which I've set to false for urlbar...
It works ("browser.urlbar.clickSelectsAll"), but does not take effect until after the browser restarts.
If you would like to change it (add/remove an observer):
search.xml#L634
and
search.xml#L640
But I don't know why it is not there. Maybe there's a reason for that...
However, see:
#1218
Last edited by GMforker on 2017-07-07, 06:37, edited 1 time in total.
-
GMforker
Unread post
by GMforker » 2017-07-07, 05:46
coffeebreak wrote:Check that these two preferencess, which are new since PM 27.3, are set to false (default) in about:config.
Code: Select all
accessibility.typeaheadfind.highlightallbydefault
accessibility.typeaheadfind.highlightallremember
(See
Release Notes for PM 27.3)
Also, "Search box" does not equal "Find bar"
-
Moonchild
- Pale Moon guru
- Posts: 35636
- Joined: 2011-08-28, 17:27
- Location: Motala, SE
-
Contact:
Unread post
by Moonchild » 2017-07-07, 10:40
There is already code that should honor this (tied to browser.urlbar.clickselectsall) -- the only possible issue would be that a browser restart would be needed.
Adding the observers should fix this.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
-
coffeebreak
- Moon Magic practitioner
- Posts: 2986
- Joined: 2015-09-26, 04:51
- Location: U.S.
Unread post
by coffeebreak » 2017-07-07, 13:16
Off-topic:GMforker wrote:Also, "Search box" does not equal ....
No it doesn't. :\ Thank you.
-
Moonchild
- Pale Moon guru
- Posts: 35636
- Joined: 2011-08-28, 17:27
- Location: Motala, SE
-
Contact:
Unread post
by Moonchild » 2017-07-08, 12:19
tommy_k wrote:since the *clickselects* toggles had instantaneous affect on urlbar I figured it would too for search box. but now I know, restart is needed for that one.
Well, it won't be needed in the future
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite