hi Fred, (In reply to Fred Stluka from comment #4) > 2. I see that you edited your comment #1 above after you saved it. I know this because I got email with your original comment text and can see that it is now different. How did you edit your existing comment? Is that something I can do for my own comments (to correct the typo of your name, for example)? Or is it an admin-only capability? When logged in, you should see a "pencil" icon, as the first in the row of icons on the RHS, in the header of your comment. That should allow you to edit it. > 3. In your original comment, you said that the bug only occurred when the tab was threaded. By that, I assume you mean that the messages are grouped into threaded conversations in the Message List. For me, that is not true. The bug occurs even after I click the "Toggle message threads" button in the column headers of the Message List to un-thread the messages. Perhaps that's why you deleted that part of your comment. Yes, the original bug affected only the message list, I believe. i.e. if the focus was in the message reader, then I could still switch. And now I see that threading affects it. As you say, things might be different, but it does seem like the same issue, or very similar. > 4. You say the Ctrl-PageUp/PageDown is a workaround. Great info! Thanks! On a Mac, there are no PageUp/PageDown keys I didn't know how to describe them. Both my Mac keyboard, and my Logitech Mac-compatible keyboard have pageup/down buttons. They're the right two buttons on the 6-button grouping that has "fn" as the top-left. > 6. In Bug 541198, mjnkml mentioned that Ctrl-Tab is yet another way to move between tabs. I tried and yes, Ctrl-Tab moves to the next tab, and Ctrl-Shift-Tab moves to the previous tab. That DOES work in TBird, just as it does Firefox, Chrome and other Mac apps. So, I guess that's another workaround I can use. Just have to re-train my fingers... I fear so; the workarounds being available has perhaps meant this bug hasn't garnered much attention.
Bug 1935799 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
hi Fred, (In reply to Fred Stluka from comment #4) > 2. I see that you edited your comment #1 above after you saved it. I know this because I got email with your original comment text and can see that it is now different. How did you edit your existing comment? Is that something I can do for my own comments (to correct the typo of your name, for example)? Or is it an admin-only capability? When logged in, you should see a "pencil" icon, as the first in the row of icons on the RHS, in the header of your comment. That should allow you to edit it. > 3. In your original comment, you said that the bug only occurred when the tab was threaded. By that, I assume you mean that the messages are grouped into threaded conversations in the Message List. For me, that is not true. The bug occurs even after I click the "Toggle message threads" button in the column headers of the Message List to un-thread the messages. Perhaps that's why you deleted that part of your comment. Yes, the original bug affected only the message list, I believe. i.e. if the focus was in the message reader, then I could still switch. And now I see that threading affects it. As you say, things might be different, but it does seem like the same issue, or very similar. > 4. You say the Ctrl-PageUp/PageDown is a workaround. Great info! Thanks! On a Mac, there are no PageUp/PageDown keys I didn't know how to describe them. Both my Mac keyboard, and my Logitech Mac-compatible keyboard have pageup/down buttons. They're the right two buttons on the 6-button grouping that has "fn" & "delete" as the left two buttons. > 6. In Bug 541198, mjnkml mentioned that Ctrl-Tab is yet another way to move between tabs. I tried and yes, Ctrl-Tab moves to the next tab, and Ctrl-Shift-Tab moves to the previous tab. That DOES work in TBird, just as it does Firefox, Chrome and other Mac apps. So, I guess that's another workaround I can use. Just have to re-train my fingers... I fear so; the workarounds being available has perhaps meant this bug hasn't garnered much attention.
hi Fred, (In reply to Fred Stluka from comment #4) > 2. I see that you edited your comment #1 above after you saved it. I know this because I got email with your original comment text and can see that it is now different. How did you edit your existing comment? Is that something I can do for my own comments (to correct the typo of your name, for example)? Or is it an admin-only capability? When logged in, you should see a "pencil" icon, as the first in the row of icons on the RHS, in the header of your comment. That should allow you to edit it. > 3. In your original comment, you said that the bug only occurred when the tab was threaded. By that, I assume you mean that the messages are grouped into threaded conversations in the Message List. For me, that is not true. The bug occurs even after I click the "Toggle message threads" button in the column headers of the Message List to un-thread the messages. Perhaps that's why you deleted that part of your comment. Yes, the original bug affected only the message list, I believe. i.e. if the focus was in the message reader, then I could still switch. And now I see that threading affects it. As you say, things might be different, but it does seem like the same issue, or very similar. > 4. You say the Ctrl-PageUp/PageDown is a workaround. Great info! Thanks! On a Mac, there are no PageUp/PageDown keys I didn't know how to describe them. Both my Mac USB (A1243) keyboard, and my Logitech Mac-compatible wireless/USBdongle keyboard have pageup/down buttons. They're the right two buttons on the 6-button grouping that has "fn" & "delete" as the left two buttons. > 6. In Bug 541198, mjnkml mentioned that Ctrl-Tab is yet another way to move between tabs. I tried and yes, Ctrl-Tab moves to the next tab, and Ctrl-Shift-Tab moves to the previous tab. That DOES work in TBird, just as it does Firefox, Chrome and other Mac apps. So, I guess that's another workaround I can use. Just have to re-train my fingers... I fear so; the workarounds being available has perhaps meant this bug hasn't garnered much attention.