38d866bf14
By default, "tooltip()" adds the tooltip element to the element in which the function is called. If a "container" option is provided the tooltip is added instead to the given element, although visually it will be shown for the element in which the function is called. The positioning context (the element that an absolute element is relative to) of the tooltips shown for the date of messages was the author row, and thus they were visible only were the author row would be visible. The author row would be clipped outside the list of messages (due to its "overflow-y" CSS property), so the tooltip shown for the date of the newest message was clipped at the top of the list of messages. Now the ChatView provides a method to specify to which element append the tooltip elements, so they can be appended to another element that does not cause clipping problems. Although right now it would be enough to add the tooltips to the chat view itself, once the chat view layout is modified to show the input field at the bottom then the same problem would arise when the chat view is shown as the main view, as the tooltips would be clipped by "#app-content". Thus, to be prepared for that change, they are added to "#app" instead. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> |
||
|---|---|---|
| .github | ||
| appinfo | ||
| css | ||
| docs | ||
| img | ||
| js | ||
| l10n | ||
| lib | ||
| templates | ||
| tests | ||
| .bowerrc | ||
| .drone.yml | ||
| .eslintignore | ||
| .eslintrc.yml | ||
| .gitignore | ||
| .stylelintrc | ||
| CHANGELOG.md | ||
| COPYING | ||
| Makefile | ||
| README.md | ||
| bower.json | ||
| karma.conf.js | ||
| package.json | ||
| run-eslint.sh | ||
| run-stylelint.sh | ||
README.md
Nextcloud Talk
Video- & audio-conferencing app for Nextcloud
Why is this so awesome?
- 👥 Private, group, public and password protected calls! Just invite somebody, a whole group or send a public link to invite to a call.
- 💻 Screen sharing! Share your screen with participants of your call. You just need to use Firefox version 52 (or newer) or Chrome with this Chrome extension.
- 🚀 Integration with other Nextcloud apps! Currently Contacts and users – more to come.
- 🙈 We’re not reinventing the wheel! Based on the great simpleWebRTC library.
And in the works for the coming versions:
- 💬 Chat integration
- 🙋 Federated calls, to call people on other Nextclouds
If you have suggestions or problems, please open an issue or contribute directly :)
Contribution Guidelines
Please read the Code of Conduct. This document offers some guidance to ensure Nextcloud participants can cooperate effectively in a positive and inspiring atmosphere, and to explain how together we can strengthen and support each other.
For more information please review the guidelines for contributing to this repository.
Apply a license
All contributions to this repository are considered to be licensed under the GNU AGPLv3 or any later version.
Contributors to the Spreed app retain their copyright. Therefore we recommend to add following line to the header of a file, if you changed it substantially:
@copyright Copyright (c) <year>, <your name> (<your email address>)
For further information on how to add or update the license header correctly please have a look at our licensing HowTo.
Sign your work
We use the Developer Certificate of Origin (DCO) as a additional safeguard for the Nextcloud project. This is a well established and widely used mechanism to assure contributors have confirmed their right to license their contribution under the project's license. Please read developer-certificate-of-origin. If you can certify it, then just add a line to every git commit message:
Signed-off-by: Random J Developer <random@developer.example.org>
Use your real name (sorry, no pseudonyms or anonymous contributions).
If you set your user.name and user.email git configs, you can sign your
commit automatically with git commit -s. You can also use git aliases
like git config --global alias.ci 'commit -s'. Now you can commit with
git ci and the commit will be signed.