When rules are grouped using the comma operator and one selector is invalid / unknown then the whole group is invalidated[1].
In this case `::-ms-input-placeholder` is unknown to Firefox and Chrome, so the `::placeholder` rule is never applied.
[1]: https://www.w3.org/TR/selectors-3/#grouping
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
- Disable style override on NcActionButton with `:not(.action-button)`
due to increased specificity over scoped Vue styles when only
`:not([class^="vs__"])` is added
Signed-off-by: Christopher Ng <chrng8@gmail.com>
- Fix user status dialog
- Add label where missing
- Move emoji picker inside input field (similar to talk)
- Fix selecting an emoji
- Fix multiselect
- Fix button with confirmation action
- Fix some other unrelated dark theme issues
- Fix select2 focus
- Run npm lint:fix
Signed-off-by: Carl Schwan <carl@carlschwan.eu>
Input fields require a 44x44 pixels target size, this makes all the
input fields and button use that size.
Bonus is that now the input fields and buttons now have the same size as
the new vue button and this looks less weird than the previous state
with controls of different sizes.
See https://www.w3.org/WAI/WCAG21/Understanding/target-size.html
Signed-off-by: Carl Schwan <carl@carlschwan.eu>
- Add visible-focus effect on each header entry
- Show focus outline when using focus-visible (keyboard navigation)
- Add polyfy for focus-visible since it's only very recently available
on webkit
- Change text for link to home button to describe the destination and
not the current page
- Improve focus effect in app sidebar navigation
Signed-off-by: Carl Schwan <carl@carlschwan.eu>
In some situations the element is still affecting the layout, especially
when a sticky is nearby.
This fix moves it properly off-screen.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
The cursor in click inputs is shown as a pointer to convey that it can
be interacted with. However, in those click inputs that can have
descendants, like buttons, the descendants may not inherit the cursor
from it (for example, a "strong" element would, but a "span" element
would not), which causes a pointer cursor to be shown on some areas of
the button and a different one to be shown on other areas. To prevent
that now all the descendants of click inputs that can have descendants
use a pointer cursor.
On the other hand, if a click input is disabled it can not be interacted
with it, so now disabled click inputs as well as their descendants show
a default cursor instead of a pointer cursor in that case.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
The cursor should be a default cursor, as the text cursor implies that
text can be introduced.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Disabled buttons use the default cursor, but as the cursor property for
primary buttons is set after the cursor property for disabled buttons
the latter is always overridden, even if the primary button is also
disabled. Due to this it is necessary to explicitly set the default
cursor for disabled primary buttons.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
