We actually want the vertical scrolling to be fixed when opening the
card details.
I am not sure where the `100` value comes from, but this makes the
scrolling happy on the swimlane view and on the lists view.
This reverts commit 74cf9e2573 "- Fix Firefox left-rigth scrollbar."
This reverts commit 9dd8216dfb.
"- Fix cards below swimlane title in Firefox by making
[previous fix](https://github.com/wekan/wekan/pull/2132/commits/f7c6b7fce237a6dbdbbd6d728cfb11ad3f4378eb)"
And this partially reverts commit dd88eb4cc
The root of the issue was that I was adding a new div and nesting
the list of lists in this new list. This resulted in some
weird behavior that Firefox could not handled properly
Revert to a code colser to v2.02, by just having the
swimlane header in a separate line, and keep only one
flex element.
fixes#2137
When a list have more cards that can fit in the screen, the members icons
are drawn on top of the swimlane below and the scrollbar is not available.
According to https://github.com/utatti/perfect-scrollbar the container
must have an `overflow: hidden` css style.
When changing the swimlane header from vertical to horizontal, dd88eb4cc1
broke this which led to this weird bug.
When `Show card count` is enabled, the lists with the card counts have
two lines of text while the lists without have only one.
This results in the box around the list headers are not of the same size
and this is visible when setting a color to the list.
If we keep the `0` value, the card might be inserted in the middle of the
list, making it hard to find it later on.
Always append the card at the end of the list by setting a sort value
based on the number of cards in the list.
When moving around the swimlanes or the lists, if one element has a sort
with a null value, the computation of the new sort value is aborted,
meaning that there are glitches in the UI.
This happens on the first swimlane created with the new board, or when
a swimlane or a list gets added through the API.
To unset the color through the IFTTT, we need a white entry.
However, we do not want to show the white enry in the hamburger
`Set Color` entry.
We can also give the `white` capability to the API, it won't hurt
and be more straightforward.
