Reported by PZajda on 2013-11-29 21:47
When skim reading is enabled, pressing comma doesn't jump to the end of the current containing element.
Others commands seems to work, but not this.
Blocked by #3688, #3689
Comment 1 by jteh on 2013-11-29 21:53
Confirmed. Those script methods need a resumeSayAllMode attribute.
Milestone changed from None to next
Comment 2 by PZajda on 2013-11-29 22:00
OK, thanks for the solution, I care of it.
Comment 3 by jteh on 2013-11-29 22:04
I notice that attribute isn't documented yet. There are plenty of examples in cursorManager, though.
Comment 4 by PZajda on 2013-11-30 00:04
OK, done, with a spelling error in my commit message I seen too late...
Pushed to Bitbucket:
Comment 5 by jteh on 2013-11-30 01:32
Thanks. Note that you can git commit --amend and then git push myremote +t3675 to fix the error if no one has pulled it yet. (FWIW, I haven't pulled it yet.) Of course, you should never do this on main branches, but it's fine for branches where no one else is collaborating yet.
Comment 6 by PZajda on 2013-11-30 12:11
I fixed my error.
I chose to delete the remote branch because git made a strange merge so I reset to my commit then amend the message to push it again.
Everything should be OK now, sorry for the setback.
Comment 7 by mdcurran on 2013-12-03 04:25
This patch looks fine. But does show up some issues to do with how sayAll skim reading has been implemented. In short if there is no container to jump to, The error is silenced, and entering or exiting of unrelated fields is announced.
These issues will be addressed in separate tickets before this one gets merged.
Comment 9 by Michael Curran <mick@... on 2013-12-05 21:38
```CommitTicketReference repository="" revision="f3b9098a87271214a119bf2581d82e22b0b133ca"
Merge branch 't3675' into next. Incubates #3675
Added labels: incubating
Comment 10 by Michael Curran <mick@... on 2013-12-18 23:49
Fixed in ac8359f and 0f4b17c
Removed labels: incubating
Comment 11 by mdcurran on 2013-12-18 23:59
Milestone changed from next to 2014.1