Open RobertHarnett opened 5 months ago
does not currently have an easy way to access it from the bottom of a article
Replacing the currently no-op tts button with an "Open in browser" button seems like a good workaound for now. (only because it's easy to implement though)
Edit: or we can place a new button or a "clickable" article title in the top toolbar
Edit: or we can place a new button or a "clickable" article title in the top toolbar
I think the article title is clickable now.
does not currently have an easy way to access it from the bottom of a article
Replacing the currently no-op tts button with an "Open in browser" button seems like a good workaound for now. (only because it's easy to implement though)
Edit: or we can place a new button or a "clickable" article title in the top toolbar
Swapping out the currently unused TTS button is a good quick fix, however I still feel the right swipe is the most elegant long term.
Ultimately as long as I can get to the webview with a one handed tap or swipe at the end of an article I'm a happy chappy regardless of the method used.
Original issue title: Swipe right on the Reading Page to open article content in webview
1. Environment
2. Describe the feature request
If I’m reading an article I should be able to swipe to the right to open the article content in Webview. Currently if I’ve read an article to the end and than subsequently decided I want to view the full webpage, usually because I want to view the article comments, I have to scroll all the way back to the top and click on the title.
This is unnecessarily cumbersome, my proposed solution would be to mimic what Reeder for iOS/Mac OS does which is a simple swipe to the right. They also use the swipe up and down for going between articles, so this UX has been established before.
Im aware of the discussion in #144 and agree that a left and right swipe should be used to move ‘laterally’ as per the material guidelines and as such should not be used for going between different articles. A right swipe to open the page in webview makes sense as the webview is ‘peer content’, it also does not currently have an easy way to access it from the bottom of a article.