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
When reading an article on iOS, if I apply a tag to the article and send it, the tag does apply and is reflected in the web browser version of wallabag, but when re-visiting the article on the iOS device, I cannot see the tags that have been applied.
Open the wallabag app on an iOS device and open an article
Tap the tag icon
Tick to select previously used tags or add a new tag and tap send
The tag does appear on the web browser version of wallabag, as seen below I tagged the article indicated in the red square with the "ansible" tag:
Yet when I revisit the same article on the iOS device, there is no indication that the article is tagged:
Improvement
Tags should remain consistent when viewing an article from any device. The tags should be able to be modified on any client.
Somewhat related to #71 it would be great to be able to sort and search articles from the iOS device by tags, similar to what can be done in the web browser.
The text was updated successfully, but these errors were encountered:
Steps to reproduce/test case
When reading an article on iOS, if I apply a tag to the article and send it, the tag does apply and is reflected in the web browser version of wallabag, but when re-visiting the article on the iOS device, I cannot see the tags that have been applied.
The tag does appear on the web browser version of wallabag, as seen below I tagged the article indicated in the red square with the "ansible" tag:
Yet when I revisit the same article on the iOS device, there is no indication that the article is tagged:
Improvement
Tags should remain consistent when viewing an article from any device. The tags should be able to be modified on any client.
Somewhat related to #71 it would be great to be able to sort and search articles from the iOS device by tags, similar to what can be done in the web browser.
The text was updated successfully, but these errors were encountered: