Tails

#2 Updated by sajolida 2015-11-24 02:43:16

• Parent task set to Feature #8590

#3 Updated by tchou 2015-12-14 09:45:59

• Assignee changed from tchou to sajolida
• QA Check set to Info Needed

I have been investigating a little:

- there is only troubleshooting in restart sections

- this sections are supposed to been seen mainly or often on mobile or print

So I would suggest to fix this point in a specific way:

- move “Most computers do not start on Tails by default. If it does you are lucky. Otherwise, if the computer starts on Debian or Ubuntu, refer to the troubleshooting section about Tails not starting at all.” from a .note to an .introduction of this step.

- rewrite it as: “Most computers do not start on Tails by default. If it does you are lucky. Otherwise, if the computer starts on Debian or Ubuntu, [=>expend this troubleshooting section].” :
- longer link while we are on mobile
- explict information about the collapse/expend behaviour.

For small troubleshooting there is an issue about about popovers Feature #10627.

#4 Updated by sajolida 2015-12-16 10:41:04

• Target version changed from Tails_1.8 to Tails_2.0

#5 Updated by sajolida 2016-01-05 17:46:05

• Parent task changed from Feature #8590 to Feature #8592

#6 Updated by sajolida 2016-01-05 21:49:39

• Assignee changed from sajolida to tchou
• QA Check deleted (Info Needed)

I agree that we should consider this as a special case. We could even drop the style inherited from #pagebody div.toggleable as it was used only on /download (that we’re going to replace) and /press (minor issue).

I’m not sure to understand when you say “from a .note to an .introduction of this step” of which step? “Open these instructions on another device” or “Tails does not start at all (troubleshooting)”?

Could we maybe instead of a link have something like this: http://searchengineland.com/figz/wp-content/seloads/2013/07/wikipedia-mobile-expandable.png?

#7 Updated by tchou 2016-01-19 11:02:44

• Assignee changed from tchou to sajolida
• QA Check set to Ready for QA

Finaly I did that:

- use more words on toogle links (more easy to click on)

- use the same style that little troubleshooting (so the user knows that he will not leave the page)

- move the first troubleshooting on top of the “Restart on the intermediary Tails” section, so the troubleshooting is more unmissable (I let the others where they are as will be less used I think)

- “Could we maybe instead of a link have something like this: ”$“:http://searchengineland.com/figz/wp-content/seloads/2013/07/wikipedia-mobile-expandable.png?” It could have been a solution, but:
- different styling and behaviours on mobile and desktop
- the question about which label to use
- more in the flow, like a section and not a subsection

Take this as a proposal.

#8 Updated by sajolida 2016-01-20 18:20:35

• related to Feature #10643: Have a responsive CSS in Tails Installation Assistant added

#9 Updated by sajolida 2016-01-20 18:20:44

• Assignee changed from sajolida to tchou
• Feature Branch set to web/10643-responsive

I think you implemented this in web/10643-responsive (7b76fe3). It’s probably good enough. Marking this as Ready for QA for you like Feature #10643.

#10 Updated by tchou 2016-01-24 13:30:48

• Assignee changed from tchou to sajolida
• QA Check changed from Ready for QA to Pass

#11 Updated by sajolida 2016-01-24 15:47:12

• Status changed from Confirmed to Resolved
• % Done changed from 0 to 100

Applied in changeset commit:476aac193c28be61e384646347a09e4aecabcc53.

#12 Updated by sajolida 2016-01-24 15:49:12

• Assignee deleted (sajolida)
• % Done changed from 100 to 0
• QA Check deleted (Pass)