Trying to use selected text from a page in an Autobook thatās triggered on right-click. The āget selected text on current pageā action seems to have some serious flaws as it only works intermittently. Often no text or even outdated text is returned.
Please note that this issue is specifically for the Autobook. I do not encounter the same issue when I turn this into a regular playbook (by removing the ātriggered on right-clickā action), so the scraper action should have access to the selected text in question.
Error message (if aplicable):
Please paste the error message below:
There is no error, this just doesn't work as intended:
- Sometimes no text is returned
- Sometimes outdated text is returned
- Sometimes the actual selected text is retuned
Steps to reproduce this issue:
Iām opening an article on a website, usually medium / substack / pocket
I select some text on the page
I use a simple Autobook with just a scraper that returns the result
I check the log to see whatās returned exactly (some pictures at the bottom)
Hi, thanks for the detailed report.
I reported this internally, but meanwhile, āWhen I right-click on a websiteā already returns the selected text if you right click on a selection, and you can access it in further actions in the playbook by clicking on āTrigger: When I right-click on a websiteā ā āSelectionā. This should be more reliable than a separate āGet selected textā action.
Well actually, I tried that first! However, so far Iāve never been able to access any of the variables within triggers. Those are all empty - always. In fact, it made me think I actually misunderstood the purpose of thoseā¦
To demonstrate this, Iāve extended the Autobook with a Merge Text step, and have also made a few additional screenshots below:
Iām getting the same results. It copies the selection, but not the Page URL, or Link. Not sure the difference between Page URL or Link, but they do not return regardless:
I hope you have been able to review the additional comments about your suggested workaround (which also doesnāt give the expected results). Perhaps you can bring this to the attention of the team working on this issue as well.
Hi @rap! Our team is still looking into it, but itās taking slightly longer to resolve than we initially anticipated. Please be patient with us. Weāve prioritized your request, and expect to have an answer for you within the next two working days.
@rap my sincere apologies for not providing an update sooner. Unfortunately, this has not been resolved yet and is still in queue. Iāll nudge the team and see when we can get this resolved.
Video recording or screenshots (optional, but recommended):
