Feature #7409
Browse the offline documentation using Yelp
100%
Description
For 1.1, we’re moving back to browsing it using the Tor Browser, but we would like to go back to Yelp.
Subtasks
| Bug #7390: In Yelp, clicking a link to an anchor opens Nautilus | Rejected | 10 |
|||
| Bug #7285: Yelp crashes when clicking a link to an anchor | Rejected | 50 |
|||
| Bug #6570: Yelp freezes while searching the offline Tails documentation | Rejected | 0 |
|||
| Feature #15633: Test Duplicati to do backups | Resolved | 0 |
Related issues
|
Related to Tails - |
Rejected | 2013-11-23 | |
|
Related to Tails - |
Resolved | 2017-11-16 |
History
#1 Updated by intrigeri 2014-06-12 16:05:50
- Tracker changed from Bug to Feature
#2 Updated by BitingBird 2015-01-02 17:17:02
If i understand correctly, Yelp is fixed in Jessie, so maybe we just give this a 4.0 milestone and no more work needed ?
#3 Updated by intrigeri 2015-01-03 11:36:46
> If i understand correctly, Yelp is fixed in Jessie,
No, see subtasks.
> so maybe we just give this a 4.0 milestone and no more work needed ?
If it was fixed in Jessie, then the correct way to express the relationship would be to flag this ticket as blocked by Feature #6171: this ticket is not in itself a blocker for Tails/Jessie.
#4 Updated by BitingBird 2015-01-08 03:06:08
- related to
Bug #6434: Notification links to the documentation should open in the help browser added
#5 Updated by Anonymous 2018-01-19 17:23:34
Do we still want this?
#6 Updated by intrigeri 2018-01-19 17:54:52
- Assignee set to anonym
- QA Check set to Info Needed
A new custom doc viewer was sneaked into a recent Tails release at the last minute to workaround a Tor Browser regression. I don’t know if it was meant to be temporary or what and the discussions about it seem to have stalled. So I guess anonym is the best person to tell what the plan is.
#7 Updated by anonym 2018-01-20 11:38:05
- Assignee changed from anonym to sajolida
intrigeri wrote:
> A new custom doc viewer was sneaked into a recent Tails release at the last minute to workaround a Tor Browser regression. I don’t know if it was meant to be temporary or what and the discussions about it seem to have stalled. So I guess anonym is the best person to tell what the plan is.
I just took the best decision I could at the time, and have no strong opinion on the long term solution. I see a stronger opinion presented by e.g. sajolida, so I suggest he is asked instead.
In any case, Bug #14962 is still open so we cannot switch back to using the Tor Browser yet.
#8 Updated by sajolida 2018-02-01 21:28:36
- related to
Bug #14962: Tor Browser >= 7.0.8 fails to render local pages correctly added
#9 Updated by sajolida 2018-05-22 13:10:29
- Assignee changed from sajolida to intrigeri
It’s not clear to me what would be the benefits of Yelp over a regular browser for our offline documentation.
See Feature #15612 about why I think that providing a consistent experience between online and offline documentation is important.
A benefit of Yelp would be to provide an offline search feature.
Is it it’s only benefit?
#10 Updated by intrigeri 2018-05-25 14:32:33
> Is it it’s only benefit?
Almost. I also see a point in using an interface that our users may still be used to (either the GNOME Help browser aka. Yelp or Firefox) and that we don’t have to maintain ourselves instead of a new, custom one. But now that the online use case has been fixed, frankly I see no reason to put lots of efforts into the offline use case.
#11 Updated by intrigeri 2018-05-25 14:36:48
- Assignee deleted (
intrigeri) - QA Check deleted (
Info Needed)
#12 Updated by sajolida 2018-06-01 18:08:18
- Status changed from Confirmed to Rejected
Ok, so I’m rejecting this very old ticket.
TODO—!!!