The problem is the entity had 0 as a default it would skip writing
it into the changeset of the query for the insert.
But the DB had a default of 1 so it would store a 1 afterwards in the db.
Having null as default on the Vote model fixes this, as then any number
is a change from the default, the mark-dirty happens and we add it to
the query.
Signed-off-by: Joas Schilling <coding@schilljs.com>
"handleSubmit" was called from an event, so the "options" were the event
itself; this did not fail, as the options were defined, but they were
useless anyway. Now the options are explicitly set.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
The "fade" class for transitions is defined in the "variables" asset, so
it needs to be imported wherever the transition is used.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Sometimes Chromium does not render one or more frames to the stream
captured from a canvas, so the canvas is now rendered several times and
for a longer period to try to avoid that issue.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Although the previous behaviour should be fine this aligns the behaviour
of removed tracks with disabled and stopped tracks.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
This ensures that other participants will receive a black video track
when no visible video should be sent, even if the browser does not
properly update a previously sent track when disabled or stopped.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Until now the stream locally shown was the stream sent to the other
peers. Now there are separate streams for each case to be able to adjust
them independently to work around specific browser behaviours.
Nevertheless, the sent stream is a single stream shared by all sender
peers, not a stream specific for each peer, so it is still generated in
the local media class, just like the local stream.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Since the removal of SCSS files the "menu-people" icon can no longer be
used directly with a CSS class. However, it is available as a Vue
component; although it would be possible to directly render the Vue
component for the icon inside the button element the whole button is
moved to Vue instead, as the other approach requires more fighting with
the styles.
As the icon will be shown with a transparent background on the header,
which uses the primary color, the fill color of the icon needs to be
explicitly set to the primary text color.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Nextcloud bot
Joas Schilling
Joas Schilling
Daniel Calviño Sánchez
Marco
Vitor Mattos