| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
mobile smartphones webbrowsers, and hide drag handles on mobile web.
Thanks to xet7 !
|
| |
|
| |
|
|
|
|
| |
Thanks to xet7 !
|
|
|
|
|
|
|
| |
immediate. Only on public board use cookies.
Comment out Collapse CSS that is not in use.
Thanks to xet7 !
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
New feature, not set visible yet, because switching to it does not
work properly yet: Collapsible Swimlanes #2804
Fix: Public board now loads correctly. When you select one of Lists/Swimlanes/Calendar view and
reload webbrowser page, it can change view. Closes #2311
Fix: List sorting commented out. Closes #2800
Fix: Errors hasHiddenMinicardText, hasShowDragHandles, showSort, hasSortBy, profile,
FirefoxAndroid/IE11/Vivaldi/Chromium browsers not working by using
cookies instead of database.
More details at https://github.com/wekan/wekan/issues/2643#issuecomment-554907955
Note: Cookie changes are not always immediate, if there is no effect,
you may need to reload webbrowser page.
Closes #2643 .
Thanks to xet7 !
|
|
|
|
|
|
|
|
|
| |
Allow moving cards in multiselect mode.
Closes #2771,
closes #2743,
closes #2704,
related #2081
|
|
|
|
|
|
|
|
|
|
|
|
| |
draggable mode.
Bug Fix #2093: the broken should be prior to file attachment feature introduced, and tested export board is working.
Thanks to whowillcare !
( xet7 merged this pull request manually from https://github.com/wekan/wekan/pull/2756 )
Closes #2093
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Thanks to Keelan !
Related #2704
|
| |
| |
| |
| |
| |
| | |
Thanks to xet7 !
Related #2081
|
|/ |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
So now at Sandstorm when loading Wekan grain, if first Sandstorm board is found,
it is opened. If first Sandstorm board is not found (it's deleted or archived),
then redirect automatically to All Boards page.
Closes #3132
|
| |
|
|
|
|
| |
Thanks to justinr1234 !
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since 7cc185ac "Properly fix horizontal rendering on Chrome and Firefox"
The rendering of the new design of the swimlanes was correct, but this
commit broke the reordering capability. Having the swimlane header at
the same level than the lists of cards makes the whole sortable
pattern fail.
2 solutions:
- revert to only have 1 div per swimlane. But this introduces the firefox
bug mentioned in 7cc185ac, so not ideal
- force the sortable pattern to do what we want.
To force the sortable pattern, we need:
- add in the helper a clone of the list of cards (to not just move the
header)
- make sure the placeholder never get placed between the header and the
list of cards in a swimlane
- fix the finding of the next and previous list of cards.
For all of this to be successful, we need to resize the swimlanes to a
known value. This can lead to some visual jumps with scrolling when you
drag or drop the swimlanea. I tried to remedy that by computing the new
scroll value. Still not ideal however, as there are still some jumps when
dropping.
Fixes #2159
|
|
|
|
|
|
| |
Thanks to xet7 !
Closes #2061
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Thanks to schulz !
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
A dependency to rzymek:fullcalendar has also been added.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This code was duplicate with the name we use to `register` the
component. A update of blaze-component removed the need to duplicate
this declaration.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This bug was introduced with the introduction of fast-render in
41b23f8. With fast-render data is available instantly after the page
logging, but calls to `Meteor.userId()` still return `null` as the
user isn't authenticated on the DDP channel yet (previously the data
was loaded on DDP after user authentication). Which mean that we know
need to reactively activate Drag and Drop on user log in.
I'm not sure why I was not able to reproduce this bug outside of
Sandstorm.
Fixes #453
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Yes Wekan need some tests. Yes I need to stop refactoring my code
when I’m halp-sleeping in my bed at 4am.
|
|
|
|
| |
Blaze-components had yet another methods rename.
|
|
|
|
|
|
| |
This version includes a more complete selection of ES2015 polyfills
that I started used across the code base, for instance by replacing
`$.trim(str)` by `str.trim()`.
|