Problems with the actualization 31.4 Topic is solved

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!
User avatar
AlexBrainbond
Newbie
Newbie
Posts: 6
Joined: 2022-11-23, 11:27

Problems with the actualization 31.4

Unread post by AlexBrainbond » 2022-11-23, 11:51

Hi, in new version 31.4, When you press the delete button the window goes back to the last one you was.
And When you press the buttot on top of Cap Lock (tab button) the selector goes to the searching bar on the top of the window.
¿Is that normal ?

Windows 10:
31.4:
32-bit or 64-bit browser:
Last edited by AlexBrainbond on 2022-11-23, 16:06, edited 1 time in total.

User avatar
AndieM
Moongazer
Moongazer
Posts: 13
Joined: 2019-04-11, 14:49

Re: Problems with the actualization 31.4

Unread post by AndieM » 2022-11-23, 14:08

Please give a full description of the problem. Without nobody could and will help you.

See: IMPORTANT: Information to include when asking for support

User avatar
AlexBrainbond
Newbie
Newbie
Posts: 6
Joined: 2022-11-23, 11:27

Re: Problems with the actualization 31.4

Unread post by AlexBrainbond » 2022-11-23, 15:14

When you are writing on a text input on one page but u want to delete the text, you press the delete button on your keyboard.
But the text is not removed.
When you press the delete button, the page you are viewing, goes to the back page you was.

User avatar
therube
Board Warrior
Board Warrior
Posts: 1650
Joined: 2018-06-08, 17:02

Re: Problems with the actualization 31.4

Unread post by therube » 2022-11-23, 15:49

Tools | Preferences -> Close the window when the last tab is closed (uncheck)

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35476
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: Problems with the actualization 31.4

Unread post by Moonchild » 2022-11-23, 18:50

I'm assuming you're talking about "backspace" here which, if you do not have a text input focused, is a shortcut key for navigating back in history.

Can you please provide a URL?

Can you please provide exact steps to reproduce the issue?
"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

User avatar
MoonWalker
Apollo supporter
Apollo supporter
Posts: 31
Joined: 2020-10-13, 15:38

Re: Problems with the actualization 31.4

Unread post by MoonWalker » 2022-11-23, 20:43

Looks like you are having trouble with shortcuts. Backspace key is a shortcut to go back to the previous page. That shortcut does not work when the cursor is active in a text box, but if you click in any place outside the text box and then press backspace, you will activate the shortcut.

 And Ctrl + L is a shortcut to place the cursor on the address bar. You are probably press Ctrl instead of cap lock or tab.

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35476
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: Problems with the actualization 31.4

Unread post by Moonchild » 2022-11-23, 21:12

We had a behavioural change this version to no longer fire keypress events for non-printable keys (so they are naturally handled by first content scripts and if unhandled, by the browser itself) so it is possible that any non-standard handling of input that is not an editable form or element no longer catches the keypress (and potentially not firing a preventDefault() as a result) if listening on keypress events, and it filtering up to the navigation instead.

We would need to know if this is a plugin issue or where it exactly occurs to reproduce and investigate, but could you please let us know as well if setting dom.keyboardevent.keypress.dispatch_non_printable_in_content to "true" helps, to confirm this is the issue, as well as more details?
"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

User avatar
AlexBrainbond
Newbie
Newbie
Posts: 6
Joined: 2022-11-23, 11:27

Re: Problems with the actualization 31.4

Unread post by AlexBrainbond » 2022-11-24, 08:49

It is an Aplication on cloud and it was made on FLEX, it isn't a normal form.
We have got 2 apps 1 on Flex(it doesn't work) and the other on Angular (it work well).
I think the language "FLEX" is the problem.
I can't provide one URL because you need a user and password to use it because is an Online ERP.

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35476
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: Problems with the actualization 31.4

Unread post by Moonchild » 2022-11-24, 12:59

Moonchild wrote:
2022-11-23, 21:12
could you please let us know as well if setting dom.keyboardevent.keypress.dispatch_non_printable_in_content to "true" helps, to confirm this is the issue
"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

User avatar
AlexBrainbond
Newbie
Newbie
Posts: 6
Joined: 2022-11-23, 11:27

Re: Problems with the actualization 31.4

Unread post by AlexBrainbond » 2022-11-24, 15:07

Moonchild wrote:
2022-11-23, 21:12
could you please let us know as well if setting dom.keyboardevent.keypress.dispatch_non_printable_in_content to "true" helps, to confirm this is the issue
No, the dom.keyboardevent.keypress.dispatch_non_printable_in_content is on "false"

User avatar
somdcomputerguy
Lunatic
Lunatic
Posts: 381
Joined: 2014-02-23, 17:25
Location: Greenbrier County, West Virginia
Contact:

Re: Problems with the actualization 31.4

Unread post by somdcomputerguy » 2022-11-24, 17:33

AlexBrainbond wrote:
2022-11-24, 15:07
Moonchild wrote:
2022-11-23, 21:12
could you please let us know as well if setting dom.keyboardevent.keypress.dispatch_non_printable_in_content to "true" helps, to confirm this is the issue
No, the dom.keyboardevent.keypress.dispatch_non_printable_in_content is on "false"
He didn't ask you, AlexBrainbond, what it was set to, he asked if setting it to true helped.
:cool: -bruce /* somdcomputerguy.com */
'If you change the way you look at things, the things you look at change.'

User avatar
AlexBrainbond
Newbie
Newbie
Posts: 6
Joined: 2022-11-23, 11:27

Re: Problems with the actualization 31.4

Unread post by AlexBrainbond » 2022-11-24, 18:00

He didn't ask you, AlexBrainbond, what it was set to, he asked if setting it to true helped.
oh yes yes, it works Thanks a lot :thumbup:

User avatar
somdcomputerguy
Lunatic
Lunatic
Posts: 381
Joined: 2014-02-23, 17:25
Location: Greenbrier County, West Virginia
Contact:

Re: Problems with the actualization 31.4

Unread post by somdcomputerguy » 2022-11-24, 18:29

AlexBrainbond wrote:
2022-11-24, 18:00
He didn't ask you, AlexBrainbond, what it was set to, he asked if setting it to true helped.
oh yes yes, it works Thanks a lot :thumbup:
Cool beans :mrgreen:
:cool: -bruce /* somdcomputerguy.com */
'If you change the way you look at things, the things you look at change.'

User avatar
Memophenon
Hobby Astronomer
Hobby Astronomer
Posts: 15
Joined: 2020-12-25, 13:15

Re: Problems with the actualization 31.4

Unread post by Memophenon » 2022-11-29, 13:53

Moonchild wrote:
2022-11-24, 12:59
Moonchild wrote:
2022-11-23, 21:12
could you please let us know as well if setting dom.keyboardevent.keypress.dispatch_non_printable_in_content to "true" helps, to confirm this is the issue
This might solve my problem with TiddlyWiki not reacting anymore on Esc, Ctrl+Enter and Ctrl+Shift+Enter in order to leave a textarea field (and possibly store its modified content). How can I set dom.keyboardevent.keypress.dispatch_non_printable_in_content to true? By putting some JS code in some JS file in some directory?

User avatar
AlexBrainbond
Newbie
Newbie
Posts: 6
Joined: 2022-11-23, 11:27

Re: Problems with the actualization 31.4

Unread post by AlexBrainbond » 2022-11-29, 15:24

Firstly, you must put in the searching bar this text: about:config
Then one alert page will apear but you will click on accept.
The third step you must to do is, put the directive on the search bar in to the page.
dom.keyboardevent.keypress.dispatch_non_printable_in_content
To end, you click 2 times to change "False" to "True"

User avatar
Memophenon
Hobby Astronomer
Hobby Astronomer
Posts: 15
Joined: 2020-12-25, 13:15

Re: Problems with the actualization 31.4

Unread post by Memophenon » 2022-11-29, 16:14

Now you've named it, it looks familiar. An old Mozilla feature, must have seen it in a previous life. And indeed, setting this property to true makes TiddlyWiki fully key-aware again.
Thanks for your help.

User avatar
Thad E G
Moongazer
Moongazer
Posts: 8
Joined: 2022-10-23, 10:38

Re: Problems with the actualization 31.4

Unread post by Thad E G » 2022-11-30, 14:40

AlexBrainbond wrote:
2022-11-29, 15:24
dom.keyboardevent.keypress.dispatch_non_printable_in_content
To end, you click 2 times to change "False" to "True"


One some forums, ctrl-I, ctrl-B, etc, add tags for italic, bold, etc. Must have been since Pale Moon update, I noticed it stopped working.

I wondered if this worked for that case, and, for two vB forums I use: it does.

Thanks

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35476
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: Problems with the actualization 31.4

Unread post by Moonchild » 2022-11-30, 16:44

Unfortunately it's either one or the other.

Some sites will break user input when keypress events are sent for non-printable keys (because they do checks on user input in real time and do not specifically handle non-printable keys, because none of the mainstream browsers do this anymore). Other sites apparently use keypress events to listen for non-printable key combinations like those formatting shortcuts and as a result break when they no longer receive these events.
It's not possible to do both at the same time.

For me it's more logical to send all keypresses to content when you have event handlers for it (i.e. our past behaviour, which is the same as having the pref flipped), but it's now the less compatible option.
Websites can solve this by listening on "keydown" instead of "keypress" if they want to catch non-printable keys.
"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

Locked