use transparent if no color definition is needed
so the color was defined only once.
add frame with --color-border
add selected page frame with --color-primary-dark
add hover page frame with --color-primary-darker
Signed-off-by: andreas kainz <kainz.a@gmail.com>
Change-Id: I49dd896cae164da3e778a56f0ca478d116b23cec
See also Strings in the menubar
Signed-off-by: Pedro Pinto Silva <pedro.silva@collabora.com>
Signed-off-by: andreas kainz <kainz.a@gmail.com>
Change-Id: I1ab6c0ca9b707839d9da174c0c48a76056a3ec04
hardcoded border colors and radius get replaced by var's
hover effect was added
::placeholder color was defined with --color-main-text
Pedro: no need to add ms vendor CSS stuff as we dropped ie
support. (And Edge support the regular property)
Signed-off-by: andreas kainz <kainz.a@gmail.com>
Change-Id: I273842fc25d6f6f91914365499a58d7823669abf
Signed-off-by: Pedro Pinto Silva <pedro.silva@collabora.com>
text which isn't selected or for anything importand,
should use --color-main-text
Signed-off-by: andreas kainz <kainz.a@gmail.com>
Change-Id: I93602996484bf877ded864954d6560aab0411f49
Adding or removing class selected looks incorrect even though it
works this way because of sending the event before we change its visibility
but the correct way should be sending it after we change its visibilty
Signed-off-by: Mert Tumer <mert.tumer@collabora.com>
Change-Id: Ibe7b48d6c4b421bd914f833883e866894366f022
We must send additional ruler state when we read
the ui defaults also class selected must be added or removed the other
way around. The rulerchanged event was sent before the correct
place and that was why it was made the opposite now it is sent
after we change the visibility.
Signed-off-by: Mert Tumer <mert.tumer@collabora.com>
Change-Id: I8e59003fef433e6692f02e144223c4e0ee833330
The cell Appearance in calc sidebar show the following commands:
- background color
- border arrange with border width
- border color
in master there is a lot of vertical space used
without additional feature
so the height was shrinked to one row only
Signed-off-by: andreas kainz <kainz.a@gmail.com>
Change-Id: I0831995ccfc18bc6625304d8faeb65fae0fea9f2
In the writer Sidebar at the Table Panel
the items from the second row will be left
aligned so no flex-end is needed.
Signed-off-by: andreas kainz <kainz.a@gmail.com>
Change-Id: I315115d4776d8431cf6df2112970651f9f36bbd3
Currently translated at 81.7% (362 of 443 strings)
Co-authored-by: Simon T <simonpmt@gmail.com>
Translate-URL: https://hosted.weblate.org/projects/collabora-online/ui/da/
Translation: Collabora Online/UI
Signed-off-by: Andras Timar <andras.timar@collabora.com>
Change-Id: If725530fe9fdc8f8c52c668bad50d9488d991afc
When saving and/or uploading fails, we have
to give up after a certain number of retries.
A new config entry, per_document.limit_store_failures,
controls the number of consecutive failures
before giving up. This prevents locking-up
documents while uploading.
Includes a new unit-test.
Change-Id: I1296df1691fcaa982df9e861d34cb946a2eda860
Signed-off-by: Ashod Nakashian <ashod.nakashian@collabora.co.uk>
Refactor UnitWOPIDocumentConflict.cpp into
WOPIUploadConflictCommon.hpp and reuse for both
DocumentConflict and SaveOnExit tests.
Change-Id: I54ec1e37e5e9c6298b12a2b2e596363683fb2e34
Signed-off-by: Ashod Nakashian <ashod.nakashian@collabora.co.uk>
Now we have multiple document conflict scenarios
that exercise different states of DocBroker and
verify correct behavior in all cases.
Change-Id: Ia1a65be686a0899776799c82c1ebfd405c92dcab
Signed-off-by: Ashod Nakashian <ashod.nakashian@collabora.co.uk>
When the last client connection is closed,
there is UI (or user) to provide input
on the document conflict dialog. In this
case, we detect that the situation is final
and unresolvable and we simply give up.
We log a warning and dump the document state
before terminating.
Change-Id: I111a446b8743a0d16b7ed8b39751a419036c927f
Signed-off-by: Ashod Nakashian <ashod.nakashian@collabora.co.uk>
When the document has been changed in storage,
we should be extra careful not to inadvertently
clobber it because we needed to force the
upload for some unrelated reason.
When in conflict, only a user can force clobbering.
Change-Id: I498a6d1c86242b059ac722d3e48c31a04a79591b
Signed-off-by: Ashod Nakashian <ashod.nakashian@collabora.co.uk>
Since we track active sessions in removeSession,
it's possible that the last session is not active.
In that case, we should set the unload flag while
saving. If we've removed it, we should mark to
destroy. And finally, we should only assert
that mark to destroy is set with active session,
not when we are left with disconnected ones.
Change-Id: I275aeafe67875fa75e0fad5438928f2f77b79a9a
Signed-off-by: Ashod Nakashian <ashod.nakashian@collabora.co.uk>
By waiting at most 2 seconds, we improve the chances
of getting the ModifiedStatus=false before we termiante
the document. This minimizes the noise of warning
of potentially lost data on exit and similarly reduces
the test failures, which test for clear termination.
Change-Id: I284693d1cdd91b1224581fdc29e6e5438ab4c0b2
Signed-off-by: Ashod Nakashian <ashod.nakashian@collabora.co.uk>
We no store the origina modified time of the document
as we receive from the storage server in string
form and send it back as-is. This avoids any
potential issues with the roundtrip of conversion
to and from a timestamp.
Change-Id: I524bea8f36c3ce62dcd00c4fe6a1e7e083287ed1
Signed-off-by: Ashod Nakashian <ashod.nakashian@collabora.co.uk>
