You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Performance, marking up even more of the page could be quite the performance hit.
How to know what characters/words/tokens are visible in the viewport - this seems difficult to do performatively, or at all.
Ideas
Here are some ideas about how to reference areas of a webpage:
Cusorless is the obvious example here. This does seem like a significant amount of work though and in the interest of thinking of other interactions lets continue...
Referencing words in the current viewport literally, for text The quick brown fox jumps over the lazy dog, take quick past fox to select/copy quick brown fox
Copying/selecting lines of text - each line could be marked up with number/letter/color hints
Use containing elements like div or other HTML elements (see image below where I added an outline to all div elements)
Leveraging the existing vscode draft capability, where you could copy a chunk and then refine more in vscode
Inspiration
A list of some other tools for inspiration:
Dense Grid reference screen with number and letter combinations
Selecting text only - possibly allowing for further refinement
Copy the requested text to clipboard directly.
Given most of the time spent using a web browser would be reading and navigating it seems that any mode that would allow you to copy text would be something that you had to switch into to allow for more markup on the page and actions to become available. Though this would impact the fluency aspect.
The text was updated successfully, but these errors were encountered:
Not at all. The reason Links which copy things to clipboard don't always work due to lack of user activation #18 happens is because we are not the ones copying to the clipboard. This happens on click and we don't know when or what will be copied to the clipboard. copy link, for example, should always work and copying other text should follow the same mechanics.
I've improved performance and I think marking the text elements of a page wouldn't have that much more impact. We'll have to see. My only concern is that to know if an element is obscured I use document.elementFromPoint, which is a bit slow. I'll try to optimize as much as I can.
This is easy to do with the Range API. The only difficulty will be getting the character position for input and textarea text since for those elements Range only gives you characters offsets and not position in the viewport.
I think cursorless is the way to go. Maybe your second option of referencing words could be interesting. My only concern would be recognition issues when we have a command like copy (<mark> | <phrase>) past(<mark> | <phrase>).
I think adding a way to show/hide hats will be necessary. Like I intend to do for hints, I think I'll implement a toggle in four levels: Global - > Tab - > Domain - > Path. So Rango will go from left to right and if the user has disabled any of the levels the hints/hats won't show.
Thinking more about it I think the toggles should be "on", "off" and "auto". That way I could have the marks show for specific pages for example. I'll probably implement that with a true, false, undefined storage variable.
This has been mentioned a few times in Slack I think but thought it wise to get an issue open for discussion and ideas!!
Usecase
Being able to fluently copy portions of a webpage to the clipboard.
Possible Issues
Ideas
Here are some ideas about how to reference areas of a webpage:
The quick brown fox jumps over the lazy dog
,take quick past fox
to select/copyquick brown fox
div
or other HTML elements (see image below where I added an outline to alldiv
elements)Inspiration
A list of some other tools for inspiration:
UX
Perhaps there should be two commands:
Given most of the time spent using a web browser would be reading and navigating it seems that any mode that would allow you to copy text would be something that you had to switch into to allow for more markup on the page and actions to become available. Though this would impact the fluency aspect.
The text was updated successfully, but these errors were encountered: