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.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:

Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

I get an runtime error. Following the official document guide on using scss variables in your project: https://material.angular.io/guide/theming-your-components.

![image](https://user-images.githubuse

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?