Material design

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

Summary 💡

Emotion-js added a new feature 'insertionPoint' to createCache in this pull request and marked previous 'prepend' option as deprecated.

But Mui's next.js example uses prepend. [You can find It he

Environment

Vuetify Version: 2.6.4
Vue Version: 2.6.13
Browsers: Chrome 98.0.4758.102
OS: Linux x86_64

Steps to reproduce

• Click on "Dropdown" button, the menu is shown under the button;
• Click on "Toggle Menu" twice;
• Click on "Dropdown" button, the menu is shown somewhere at the left;

Expected Behavior

It should work in a stable way. Menu should be

Documentation Feedback

According to the documentation, when disabling a select by setting a boolean value to [disabled] in the HTML template, it gives a warning as follows.

It looks like you're using the disabled attribute with a reactive form directive. If you set disabled to true
      when you set up this control in your component class, the disabled attribute will actually be set

Is your feature request related to a problem? Please describe.
Currently Quasar Modes support TS files (for Electron and PWA modes), but the CLI isn't generating them out of the box.

Additional context
We need to create the TS version of all current files in these folders:

• https://github.com/quasarframework/quasar/tree/dev/app/templates/bex/js
• https://github.com/quasarframework/

What did you do?

Hi, many thanks to all the people maintaining the library and providing support ❤️.
I use a CAEmitterLayer to make some confettis pop as soon a view is displayed. When Hero is used to transition (wit

Is your feature request related to a problem? Please describe.
I want to have several MaterialButtons for which I want to control whether they're checked or not. This involves listening to the buttons' onClick events and setting proper checked state for each of them. However, sometimes I want a button that's checked to stay checked after being clicked. This is now not possible because the

Not a single form field has a label. These designs are not usable and the patterns presented should be discouraged.

I suggest adding a validation check like Nu Validator, aXe, lighthouse, etc. to show all the places this markup is invalid.

Bug explanation

When I click twice on a field, its entire row becomes grey and my clicks on the field are ignored (can't edit the value), until I click on another field in another row. It seems to be very unintuitive.

I don't expect two clicks on a field to result in not being able to edit that field anymore.

I use the DataGrid like this:

<Grid>
    <TabControl TabStripPlacem

Is there any way to implement horizontal radio button group?