Skip to content

feat!: treat navigateToWebContent same as other guidepup methods - #44

Merged
cmorten merged 4 commits into
mainfrom
feat-treat-navigate-to-web-content-same-for-capture
Jul 21, 2026
Merged

feat!: treat navigateToWebContent same as other guidepup methods#44
cmorten merged 4 commits into
mainfrom
feat-treat-navigate-to-web-content-same-for-capture

Conversation

@cmorten

@cmorten cmorten commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Issue

No issue

Details

Currently .navigateToWebContent() behaves differently to other Guidepup commands.

This is a breaking change to update the interface to start taking an options argument, to align the interface and behaviour, starting with support for the capture flag:

  • When true the full spoken phrase of the final command to place the screen reader cursor on the first item of the web content is captured in full
  • When "initial" the initial spoken phrase of the final command to place the screen reader cursor on the first item of the web content is captured
  • When false no spoken phrases are captured

CheckList

  • Has been tested (where required).

@cmorten cmorten changed the title feat: treat navigateToWebContent same as other guidepup methods feat!: treat navigateToWebContent same as other guidepup methods Jul 21, 2026
@cmorten
cmorten merged commit 248b75c into main Jul 21, 2026
36 of 42 checks passed
@cmorten
cmorten deleted the feat-treat-navigate-to-web-content-same-for-capture branch July 21, 2026 22:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant