Commit Graph

8 Commits

Author SHA1 Message Date
Ramón Souza
7514066fc3
fix: Client can't load in certain cases (#20336)
* move settings

* remove meteor cache files
2024-05-29 09:26:11 -04:00
João Victor
3c39dc0b8c migrate userChangedLocalSettings 2024-01-30 10:03:11 -03:00
Arthurk12
8312e235f8 fix(wake-lock): remove the activation notification
Removes the activation notification for the wake lock to reduce visual noise.
2023-08-23 10:06:33 -03:00
Arthurk12
c52a35834e feat(wake-lock): enable implicit activation based on the default setting
This commit removes the wake lock activation toast along with the
enable/disable buttons, implementing the wake lock implicit activation
behavior. The wake lock feature is implicitly activated if the
`defaultSettings.application.wakeLock` in the `settings.yml` file is set
true. For mobile devices that do not support the API or fail when
requesting a wake lock, toasts are raised explaining that calls will be
dropped when the screen turns off.

In cases where `defaultSettings.application.wakeLock` is set false, users
can enable the wake lock manually through the settings menu.
2023-08-11 17:42:20 -03:00
Arthurk12
7b57565fc5 fix(wake-lock): settings attribute name 2023-07-26 17:38:34 -03:00
Arthurk12
5d1611811a fix(wake lock): change request return value
Wake lock request function returns a boolean indicating whether there was an
error or not.
2023-06-14 13:38:06 -03:00
Arthurk12
72eee8aa92 refactor(wake-lock): better button names 2023-06-14 12:53:44 -03:00
Arthurk12
f880e56a1e feat(wake-lock): prototype
Adds wake lock feature, which is available only for mobile users using
browser with support to the given API.
When an user using a supported device joins the meeting, a toast is
displayed offering to activate the feature.
Adds a toggle under settings menu to activate/deactivate it.
2023-06-13 16:22:02 -03:00