-
-
Notifications
You must be signed in to change notification settings - Fork 642
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When reporting URL of a link use caret position instead of navigator object #14723
Conversation
@XLTechie You may want to review / test this. |
This comment was marked as outdated.
This comment was marked as outdated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this will be fine. I'm not really sure if it covers more common use cases, but it appears to be slightly more flexible, at the cost of making the review cursor a bit less useful for link identification with some configurations. That probably won't be a problem for most users, and as stated, most likely won't notice either way.
@lukaszgo1 As an aside, you may want to handle the case of the very first link/graphic (Ctrl+Home position) on the Appveyor website. Noticed when downloading the try build for this PR in Firefox. "Not a link" is not announced, yet there is no link. Perhaps if Value is None, we should also announce "not a link"? I would like to say "Link has no apparent destination", because it might still be clickable somehow. If you try to open the Window version of reportLinkDestination, this happens:
If you just try the speaking report, you get the following (dev info included):
|
The only hypothetical case I can think of would be a link which is not reachable in browse mode, and is not focusable. I haven't seen such a control anywhere, so I believe this case can be safely ignored.
I've implemented your suggestion, since apparently links with no |
See test results for failed build of commit 089b35eba6 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would the user guide wording be more correct as "speaks the destination URL of the link at the caret position or current focus" (as it tries the caret position first?)
See test results for failed build of commit 8aafd79a6c |
See test results for failed build of commit 12ca9ea044 |
@lukaszgo1 @seanbudd @XLTechie The "Report Destination URL" feature seems to be rather inaccurate or problematic at the moment. I'm using the latest alpha release )27981), and NVDA+K, when pressed on some links, just says "Blank".
|
@lukaszgo1 @XLTechie @seanbudd Should I create an issue for the bug I reported in my previous comment, or is the comment enough? |
@amirsol81 I cannot reproduce this in latest Firefox Nightly. Could you please create a new issue. In the bug report please mention what web browser you';re using, and if this is a regression from this PR, i.e. if this worked when the URL was reported for the navigator object. |
yes, please create an issue. Comments on closed PRs are easily lost. |
@seanbudd Thanks - I will. |
Link to issue number:
Closes #14659
Summary of the issue:
In #14583 @XLTechie added a global commands which allows to report a URL for the link at the position of the navigator object. While this is a huge improvement compared to either having copy the URL to the clipboard or accessing the URL from the status bar from the web browser, the fact that these scripts report destination for the link at the navigator object rather than focus / caret position makes their usage impractical for people who prefer to work with review cursor / navigator object not following focus / caret.
Description of user facing changes
When user requests URL of a link NVDA reports URL of a link at the position of the caret / focus.
Description of development approach
Script for reporting URL was modified so that it first tries to get an object at the current caret position, and if that fails from the focused object. User guide and documentation for global commands were updated accordingly.
After @XLTechie's review it was noticed that the script fails to work for links without
href
attribute, as part of this PR I've added handling for such links.Testing strategy:
Tested various objects which are links, linked graphics, and non links in both focus and browse mode, in Firefox and IE.
Known issues with pull request:
None known
Change log entries:
Changes
Bug fixes:
href
attribute NVDA is no longer silent - the fact that the given link has no destination is reported instead.Code Review Checklist: