You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you browse through the community forum we can see several questions regarding slight adaptions of the style. This usually requires de-minifying the all.css file and apply changes there. However all the changes get lost after each update.
The DevOps life would be easier, if a custom.css file would be included, which does not get updated automatically.
Two observations with all.css when customizing it:
We had to remove the 100% lines two times, otherwise links can not be clicked on the WelcomePageAdditionalContent.html page on the bottom:
For the other problems, you have with !important and position you can create a PR with the changes and we can review and merge it to be available in future versions.
Or include some kind of sample for testing with the PR or here in the issue so we can make sure if we need changes to make it compatible with your example and our branding for meet.jit.si ... Thank you.
For the links problem that is strange, but you can check the welcomepage of https://meet.jit.si, there are already links about privacy policy and terms, and the app store/google store links, you can check how that works.
If you browse through the community forum we can see several questions regarding slight adaptions of the style. This usually requires de-minifying the
all.css
file and apply changes there. However all the changes get lost after each update.The DevOps life would be easier, if a
custom.css
file would be included, which does not get updated automatically.Two observations with
all.css
when customizing it:We had to remove the 100% lines two times, otherwise links can not be clicked on the
WelcomePageAdditionalContent.html
page on the bottom:In order to make use of another font defined later in
all.css
we had to removeimportant!
at the end ofThe text was updated successfully, but these errors were encountered: