1323301 - Ctrl keys do not work properly when using gtk3

Status: UNCONFIRMED

(SeaMonkey :: General, defect)

Description

[cloos]

It looks like ctrl is treated as alt in some cases.

Eg, Ctrl-a selects all like Alt-a does, rather than moving to the start of the line like it is supposed to.

But Ctrl-e opens the composer window, like ctrl-4 is supposed to.

Ctrl-n and Ctrl-p when editing no longer move to the next and previous line like they are supposed to.

Things still worked with 2.42.

Comment 1

[cloos]

For comparison, this all still works properly in FF50.

Comment 2

[Rainer Bielefeld]

(In reply to cloos from comment #0)
@reporter:
I haven't a clue what your problem might be, nearby all relevant information is missing in the report.
For example "Ctrl-a selects all ...": At least for Windows OS that is what it should do: <https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/keys_general.mspx?mfr=true>

Please:
a) Contribute a problem related step by step instruction containing every 
   key press and every mouse click how to reproduce your problem due to 
   <https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines>
   (similar to report in Bug 1139273)
b) Attach screenshots with comments if you believe that that might explain the 
   problem better than a text comment. Best way is to insert your screenshots
   into a OOo or LibreOffice DRAW document and to add comments 
   that explain what you want to show (attach .png or PDF from source document)
c) add information 
c1) concerning your Operating System (Version, Distribution, Language)
c2) concerning your SM localization (UI language, Locale setting)
c3) SM settings that might be related to your problems 
    May be you should attach a copy of menu 
   'Help → Trouble shooting information”' as a text document
c4) how you launch SM (Double click on document? console? …)
c5) Whether problem persists in safe mode without add-ons
c6) Whether problem persists with blank new profile
c7) everything else crossing your mind after you read linked texts
d)  An URL for a web page where you observe the problem.

Comment 3

[cloos]

This is standard functionality which has been in mozilla, seamonkey and even firefox since the start.

And which stopped working only as of 2.46.  But still works in ff50.

When editing, either in the url bar or in an input box, C-a always is supposed to move the cursor to the start of the current line, C-e to the end, C-n, C-p, C-b and C-f to the next line, previous line, back a glyph or forward a glyph.

Very early on jwz added a pref to control it, named something like emacs editing keys, but for the last several years it was always on.

There is a possibility that the bug is related to gtk3 instead of gtk2.

But anyway this is basic stuff which has *always* worked.  And should continue to work.

Comment 4

[Rainer Bielefeld]

Attachment: shortcuts.xhtml form SeaMonkey 2.41

Might be some OS-hodgepodge with the shortcuts? If yes this one might be an "OS Integration" bug.

@cloos:
Can you please confirm additional information a ... d due to my request? The problem might be related to some bad interaction with add-Ons or whatever else

e) It would be great to have a check for latest help (download Langpack, 
   unzip,  ...) whether there have been changes. I doubt, but you never 
   know.
f) A complete list with wrong working shortcuts (as attachment.txt) based on
   latest shortcuts.xhtml would be useful

Comment 5

[cloos]

I've recompiled against gtk2.  Everything works again.

So this only breaks when using gtk3

Comment 6

[cloos]

Oh, and I confirmed the bug was present in a pristine profile before switching back to gtk2.

I'm looking at shortcuts.xhtml now.

Comment 7

[cloos]

shortcuts.xhtml doesn't mention the editing keys in its Text Field Shortcuts section.

That is another bug.

And the claim in that section that C-a does select all text rather than beginning of line is false.