Vue3 does not replace the element while mounting but only renders within
(replace inner HTML).
So it would result in two stacked `<main>` elements which is invalid and
an accessibility issue.
Instead we just use a `<div>` element for mounting.
For Vue2 apps this does not change anything as the whole element will be
replaced with a new `<main>` element.
For vanilla apps this will slightly decrease the accessibility as the
main landmark is now missing, but this is not a hard accessibility issue
as it would be for Vue3 apps having two main elements.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
This removes custom rendering code an replaces it with the declarative menu actions.
Also adjust the template to allow the Vue UI to mount.
Custom entries still are possible.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
Fix other background-positions
Minor fix in link button icon position
Update header left and right to start and end
Signed-off-by: Mostafa Ahangarha <ahangarha@riseup.net>
When using iOS and focussing an input element the view should not be zoomed.
So if we set a maximum scale iOS will not auto-zoom but still allow users to zoom.
But we can not do this by default as this will disable user zoom on Chrome.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
This way we use the CSP nonce for dynamically loaded scripts.
Important to notice: The CSP nonce must NOT be injected in `content` as
this can lead to value exfiltration using e.g. side-channel attacts (CSS selectors).
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
Previously the footer was empty, but the backdrop was still shown.
This hides the footer if no text content was defined.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
This will tell the browser not to translate the text on the page,
since this is very confusing given the good existing translation
support in Nextcloud and the fact that the language the Nextcloud
UI is set to might not match the language the content of the
instance is in, leading to surprising effects.
Better to disable it and remove the confusion.
Fixes#34857
Signed-off-by: Arnout Engelen <arnout@bzzt.net>
The future is TOAST 🍞
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
X-UA-Compatible and X-Download-Options headers are interpreted or relevant for Internet Explorer only. With the deprecation of Internet Explorer support in Nextcloud 20 and planned support removal already in Nextcloud 22, these became obsolete and are hereby removed, including their removal from setup checks.
Signed-off-by: MichaIng <micha@dietpi.com>
To continue this formatting madness, here's a tiny patch that adds
unified formatting for control structures like if and loops as well as
classes, their methods and anonymous functions. This basically forces
the constructs to start on the same line. This is not exactly what PSR2
wants, but I think we can have a few exceptions with "our" style. The
starting of braces on the same line is pracrically standard for our
code.
This also removes and empty lines from method/function bodies at the
beginning and end.
Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
This makes possible to navigate to the menu toggle using the keyboard,
as well as being semantically more correct.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
SebastianKrupinski
skjnldsv
Christopher Ng
Ferdinand Thiessen
Kostiantyn Miakshyn
provokateurin
Mostafa Ahangarha
Grigorii K. Shartsev
Andy Scherzinger
Andrii Rublov
Joas Schilling
Luka Trovic
Côme Chilliet
julia.kirschenheuter
Arnout Engelen
Vincent Petry
Julius Härtl
MichaIng
Christoph Wurst
Christian Wenz
Gary Kim
Daniel Calviño Sánchez
Dominik Wasielewski
Roeland Jago Douma
Michael Weimann
Morris Jobke