Make left sidebar hidable in task view

[salmenf]

I don't know if this is already possible right now, but I couldn't figure it out with the docs, so here goes a feature request:

Is your feature request related to a problem? Please describe.
Right now, the annotation interface feels a bit crowded for my use case: In my scenario, an end user follows a hyperlink to one specific task which he completes (example URL: /projects/1/data?tab=1&task=1). The left sidebar really becomes unnecessary then.

Describe the solution you'd like
A project setting to hide the left sidebar while in task view. It needs to be a project settings so users don't need to set this up manually each time they annotate.

Describe alternatives you've considered
A way to insert CSS that styles the whole interface. This would be a kind of "escape hatch" for many use cases where people want to change the interface in some way. However, it's a bit hacky and might have security implications, so the solution above would be just fine for now.

[makseq]

@salmenf Have you tried to use Label stream mode? The blue button on the data manager with Label All Tasks text.

[salmenf]

Thanks for the tip! That view looks better for my use case, but I see no way to link to a specific task in that view, since the URL always remains the same no matter which task is shown: /projects/1/data?tab=1&labeling=1
With the other view, I can provide a link to a specific task, for example: /projects/1/data?tab=1&task=10

So, unfortunately, that doesn't solve the problem, unless there's some way to link to a specific task in Label stream mode.

[salmenf]

For other people who might have this issue: I found a somewhat hacky workaround.
Using this, you can actually insert a <style> tag. Then you should be able to add any styling you want to the page. Using your browser's inspector, you can then find the class names of the elements you want to target. Obviously, this is a hacky solution that is very brittle: If the class names change, for example, it will break.

[dentalala]

It's actually not a bad idea to use <style>. Yes, it can break if class names will change, but it's also clear how to fix. We'll consider making task list hideable when working on interface, thank you for the feedback.