Material design

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

Current behavior 😯

I'm implementing async load with pagination with the Autocomplete.
When the listbox is open and the user scroll to the bottom, we load the next page and add the new options.
After adding, the position of the scroll on the listbox is reseted and

Environment

Vuetify Version: 2.4.3
Vue Version: 3.0.5
Browsers: Chrome 88.0.4324.96
OS: Mac OS 10.15.7

Steps to reproduce

• open the type week sample code by codepend
• set calendar type to custom-daily
• set start=2019-01-05, end=2019-01-10,
• set Thomas Birthday as `start: '2019-01-01', end:

Documentation Feedback

Steps to Reproduce

1. Go to the Autocomplete optgroup Example.
2. Click the "View Code" button

Result

One of the tabs for viewing the code reads ./autocomplete-optgroup-example.html.

<img width="1366" alt="Screen Shot 2022-03-16 at 8 46 07 AM" src="https://user-ima

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

Description: Extra space for a separator is allocated under the last element, even if lastItemDecorated = false.

Expected behavior: If lastItemDecorated = false, there should be neither a separator nor a space allocated for a separator under the last element.

How to check:

• Open DividerItemDecorationDemoFragment.java from :catalog project
• Configure divider as follow

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.

Right now the Getting Started section in the README is a bit outdated.

People who are just getting started with this library are not likely to have all of the dependencies needed (latest version of VS, .NET Core

Is there any way to implement horizontal radio button group?