Problem with ctrl+alt+home
|
Hello.
I have a problem with keyboard shortcut ctrl+alt+home in a table. It didn't move me to the first column. Please, could You look on It? Thank You. Marco |
|
|
|
People, I have found It.
toggle quoted message
Show quoted text
It didn't work on Firefox. Please, could You look on It? Every keyboard shortcuts works just fine, eccept only ctrl+alt+home. Marco Dňa 16. 1. 2023 o 22:25 Marco Oros via groups.io napísal(a): Hello. |
|
|
|
Please, try with Firefox second table in this page and press ctrl+alt+home.
toggle quoted message
Show quoted text
https://en.wikipedia.org/wiki/List_of_largest_cities Dňa 16. 1. 2023 o 22:30 Marco Oros via groups.io napísal(a): People, I have found It. |
|
|
|
Gene
This appears to be a problem with the latest version of NVDA. I tried with the previous version and I had no such problem.
toggle quoted message
Show quoted text
Gene On 1/16/2023 3:38 PM, Marco Oros wrote:
Please, try with Firefox second table in this page and press ctrl+alt+home. |
|
|
|
Yeah, but I don't want to downdate NVDA due to this.
toggle quoted message
Show quoted text
Please, where can I send this message to developers? To Github of NVDA? I think, that many people uses Firefox, althought many prefer to use Chrome. Problem is maybe with clickable items in tables in Firefox. So, where to contact developers and inform about It? Marco Dňa 16. 1. 2023 o 22:48 Gene napísal(a): This appears to be a problem with the latest version of NVDA. I tried with the previous version and I had no such problem. |
|
|
|
Hi, Does this happen if add-ons are disabled? Cheers, Joseph |
|
|
|
Gene
I checked with add-ons disabled and it does.
toggle quoted message
Show quoted text
Gene On 1/16/2023 3:58 PM, Joseph Lee wrote:
|
|
|
|
Quentin Christensen
Try disabling add-ons. It seems like there are a couple of add-ons which people have found to cause trouble for the table navigation commands. To do that, press NVDA+q, then down arrow to "Restart with add-ons disabled" and press enter. If that fixes it, try enabling add-ons one at a time to see which one is causing problems, and see if there is a newer version of that add-on or make the decision whether to disable that add-on for now to use the table commands, or enable it and not be able to use table navigation for now. Otherwise, we would need more information about where this table is (what program), what version of the program / windows / nvda, what you've tried, etc. Quentin. On Tue, Jan 17, 2023 at 8:25 AM Marco Oros <marco.oros93@...> wrote: Hello. --
Quentin Christensen Training and Support Manager Training: https://www.nvaccess.org/shop/ Certification: https://certification.nvaccess.org/ User group: https://nvda.groups.io/g/nvda Facebook: http://www.facebook.com/NVAccess Twitter: @NVAccess |
|
|
|
Quentin Christensen
I can replicate this with that table with NVDA 2022.4 in Firefox. It works as expected in Chrome It works as expected with NVDA 2022.3.2 The move to first column command NVDA+control+home works correctly in some tables, such as in the NVDA user guide in Firefox with NVDA 2022.4. Possibly related to the merged cells in the header in that Wikipedia table? I wrote an issue up here: https://github.com/nvaccess/nvda/issues/14552 Quentin. On Tue, Jan 17, 2023 at 9:02 AM Gene <gsasner@...> wrote:
--
Quentin Christensen Training and Support Manager Training: https://www.nvaccess.org/shop/ Certification: https://certification.nvaccess.org/ User group: https://nvda.groups.io/g/nvda Facebook: http://www.facebook.com/NVAccess Twitter: @NVAccess |
|
|
|
I am going to post this here because it is a classic example of where this needs to be repeated: For the love of heaven, if you (any you) are having a problem of significance (and this one is) you MUST GIVE YOUR ECOSYSTEM INFORMATION. At a MINIMUM, that includes:
1. Windows Version (and build, if we're talking Windows 10 or 11). 2. NVDA Version - that's actual version number, not "latest NVDA," we all know how often that proves not to be the actual case 3. Program Name AND version that is not interacting with NVDA as expected. It is really not fair to anyone, including members here who wish to attempt to assist, to have to guess about or ask for this information. It's basic information that should be offered, period, end of sentence, no negotiation and don't bother complaining. Just do it. Also, if you intend to enter issues on GitHub for NVDA, you need to be prepared with the necessary information in order to do so, and it is way more than just the ecosystem basics requested above. Here is a text copy of the GitHub Issue Report for NVDA and you are always going to be filling out the vast majority of the requested information, and you absolutely will have to have performed the steps such as restarting the computer, restarting NVDA with add-ons disabled, etc., or you will be made to do so before the issue is pursued, at all. --------------- <!--This issue report is in three sections: Problem Description, System Configuration, and Other Questions.--> Problem Description ### Steps to reproduce:
### Actual Behavior:
### Expected Behavior:
### System configuration #### NVDA Installed/Portable/Running from some other source:
#### NVDA Version:
#### Windows Version:
#### Name and Version number of the other software in use when reproducing the issue:
#### Other information about your system (e.g., Make & Model, Graphics Card, etc.):
### Other Questions #### Does the issue still occur after restarting your computer?:
#### Have you tried using any other versions of NVDA to reproduce the problem? If so, please give the version number(s) and behavior(s):
#### If you disable add-ons, is your problem still occurring?:
#### Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's Tools menu?: --------------- It is getting really old having to repeat the request for ecosystem information over and over and over again. It should long ago have been recognized as essential information, not optional. -- Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit It is much easier to be critical than to be correct. ~ Benjamin Disraeli, 1804-1881 |
|
|
|
Hi, Confirmed - I'm also noticing that Firefox says 14 columns whereas Chromium-based browsers (Chrome and Edge) are reporting 13 columns, so I suspect a combination of Gecko's rendering of this table and NVDA getting confused about certain properties of this table (tested with: Firefox 108.0.2, Chrome 108, Edge 109). Cheers, Joseph |
|
|
|
Quentin Christensen
Thanks Brian! This issue is actually a really good example. The initial post in this thread simply mentions a problem with control+alt+home in a table. But if you test in Chrome, it works fine. If you test on a table like the ones in the NVDA user guide (the first one I would try based only on that info), it works fine. Only when we got more information could we narrow it down: That the user was using Firefox, and an example table from Wikipedia was given, AND that navigation works correctly on this table with older versions of NVDA. With that information, I can replicate that yes, there does seem to be a problem with that particular table command (but not all table commands) on that table with NVDA 2022.4 in Firefox. Knowing that it works in NVDA 2022.3.2 and that this table is navigable in Chrome with 2022.4 and that the command works as expected with 2022.4 in another table (our user guide), I am confident should give our developers enough information to work out where the issue is. As it happens, some add-ons have also caused issues with table navigation commands after updating NVDA. Without more information, the initial assumption could be made that this was likely also the case for this user. So yes, please provide as much information as possible when reporting something. Kind regards Quentin. On Tue, Jan 17, 2023 at 9:40 AM Brian Vogel <britechguy@...> wrote: I am going to post this here because it is a classic example of where this needs to be repeated: For the love of heaven, if you (any you) are having a problem of significance (and this one is) you MUST GIVE YOUR ECOSYSTEM INFORMATION. At a MINIMUM, that includes: --
Quentin Christensen Training and Support Manager Training: https://www.nvaccess.org/shop/ Certification: https://certification.nvaccess.org/ User group: https://nvda.groups.io/g/nvda Facebook: http://www.facebook.com/NVAccess Twitter: @NVAccess |
|
|
|
On Mon, Jan 16, 2023 at 05:53 PM, Quentin Christensen wrote:
- Thank you, and don't I know it. You mention, and it's something I often do as well, that when the issue is with using NVDA with a web browser, not only is the web browser and version information needed, so is at least one URL or several URLs where the issue can be replicated along with the exact steps needed to replicate it. You can't fix what you can't reproduce, and often the precise steps a user takes may directly play in to what triggers an issue. I've seen plenty of instances where others attempting to replicate something couldn't only because "how I go about doing this" differs from the way that the issue reporter does. And that does not mean that the issue reporter is doing anything wrong or incorrectly. It simply means that since "the road being taken to Rome" can matter, we need to know what road that is. -- Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit It is much easier to be critical than to be correct. ~ Benjamin Disraeli, 1804-1881 |
|
|
|
Yes, It is same, when add-ons are disabled. But problems are only in Firefox in tables with clickable objects, for example in page, which I have sent to You. Marco Dňa 16. 1. 2023 o 22:58 Joseph Lee
napísal(a):
|
|
|
|
Can the groups.io signature be set to give that automatically even on a reply like how I hopefully have mine? At least for this group?
T
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Monday, January 16, 2023 2:41 PM To: nvda@nvda.groups.io Subject: Re: [nvda] Problem with ctrl+alt+home
I am going to post this here because it is a classic example of where this needs to be repeated: For the love of heaven, if you (any you) are having a problem of significance (and this one is) you MUST GIVE YOUR ECOSYSTEM INFORMATION. At a MINIMUM, that includes: <!--This issue report is in three sections: Problem Description, System Configuration, and Other Questions.--> Problem Description ### Steps to reproduce:
### Actual Behavior:
### Expected Behavior:
### System configuration #### NVDA Installed/Portable/Running from some other source:
#### NVDA Version:
#### Windows Version:
#### Name and Version number of the other software in use when reproducing the issue:
#### Other information about your system (e.g., Make & Model, Graphics Card, etc.):
### Other Questions #### Does the issue still occur after restarting your computer?:
#### Have you tried using any other versions of NVDA to reproduce the problem? If so, please give the version number(s) and behavior(s):
#### If you disable add-ons, is your problem still occurring?:
#### Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's Tools menu?:
--------------- Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit It is much easier to be critical than to be correct. ~ Benjamin Disraeli, 1804-1881 -- ---------- Sarah Alawami, owner of flying Blind. Visit my website to read my story. Windows 11 22H2 (x64) build 22621.963 NVDA Version: 2022.3.3 Microsoft 365 MSO (Version 2211 Build 16.0.15831.20098) 64-bit |
|
|
|
On Mon, Jan 16, 2023 at 08:23 PM, Sarah k Alawami wrote:
Can the groups.io signature be set to give that automatically even on a reply like how I hopefully have mine?- Yes, and your hopes are dashed. I mentioned this in an admin notice I sent in December 2022: I'm using the Groups.io signature option, which allows all users, whether by email or the web interface, to set up a signature that will be used by email contributions and/or web posts. This is on the Subscription page for each and every group that you're subscribed to, and is separate for each and every group. Since it's an edit box for the signature and two checkboxes to control when it's used, I didn't go into further detail. I personally think it's better to create your signature with the exact formatting you'd like it to have in MS-Word or another word processor, then copy it and paste it in to the edit box. Then select one the other or both of the checkboxes to control when it's used. Pretty much what you fill in for your signature on that page is what will be used. And when/where it's used, for email messages you send to that group or for web posts, is controlled by the two checkboxes associated with the signature. -- Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit It is much easier to be critical than to be correct. ~ Benjamin Disraeli, 1804-1881 |
|
|
|
On Mon, Jan 16, 2023 at 08:33 PM, Brian Vogel wrote:
I'm using the Groups.io signature option, which allows all users, whether by email or the web interface, to set up a signature that will be used by email contributions and/or web posts.- In re-reading this, I don't like the phrasing I used, because the Groups.io signature feature itself is accessed strictly via the Groups.io web interface. And it's on the subscription page for each given group where you can set your signature for that group. You cannot, to my knowledge, actually set up a signature via e-mail. But once you have that signature in the edit box, it's the two checkboxes associated with it that determines whether that signature will be appended to messages sent to the group via email, using the web interface to post, or both. Like any online facility, there are certain things you must do on the web interface for your personal account, and in this case each group associated with your account, as you may very well want different signatures for each group. If you don't, then you can copy and paste to each Signature edit box for each group and choose your checkboxes for that group. Signatures are at the level of a group, not Groups.io as a whole. -- Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit It is much easier to be critical than to be correct. ~ Benjamin Disraeli, 1804-1881 |
|
|
|
Yep I saw that and saved it for this group, I think? If not I will fix that post haste, well, tomorrow.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Monday, January 16, 2023 5:34 PM To: nvda@nvda.groups.io Subject: Re: [nvda] Problem with ctrl+alt+home
On Mon, Jan 16, 2023 at 08:23 PM, Sarah k Alawami wrote:
- Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit It is much easier to be critical than to be correct. ~ Benjamin Disraeli, 1804-1881 -- ---------- Sarah Alawami, owner of flying Blind. Visit my website to read my story. Windows 11 22H2 (x64) build 22621.963 NVDA Version: 2022.3.3 Microsoft 365 MSO (Version 2211 Build 16.0.15831.20098) 64-bit |
|
|
|
Ron Canazzi
Hi Group,
Wasn't there discussion about broken table navigation and I or someone else narrowed it down to the NVDA Global command enhancements add on? I think you had to go in deep and disable one item of the add on. I forget which one. On 1/16/2023 5:34 PM, Quentin
Christensen wrote:
-- Signature: For a nation to admit it has done grievous wrongs and will strive to correct them for the betterment of all is no vice; For a nation to claim it has always been great, needs no improvement and to cling to its past achievements is no virtue! |
|
|
|
Quentin Christensen
Looks like there have been several different issues - one was caused by the add-on - the one from this thread seems to be related to one particular command (Move to first column) in Firefox on some tables and happens without any add-ons installed. On Tue, Jan 17, 2023 at 4:41 PM Ron Canazzi <aa2vm@...> wrote:
--
Quentin Christensen Training and Support Manager Training: https://www.nvaccess.org/shop/ Certification: https://certification.nvaccess.org/ User group: https://nvda.groups.io/g/nvda Facebook: http://www.facebook.com/NVAccess Twitter: @NVAccess |
|
|