Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Color palette is not responsive in styles/index.html #5361

Open
rushikeshbagul opened this issue Aug 30, 2021 · 1 comment
Open

Color palette is not responsive in styles/index.html #5361

rushikeshbagul opened this issue Aug 30, 2021 · 1 comment

Comments

@rushikeshbagul
Copy link

** PLEASE READ THIS BEFORE FILING AN ISSUE **

Feature Requests / Breaking Changes in mdl-1.x

The MDL core team has actively begun work on the next major version of MDL, dubbed MDL v2. Because we are a small team that's hyper-focused on delivering the best Material Design Library possible for the web, it is highly unlikely that we will be actively working on new features or making backwards-incompatible changes for MDL as it currently exists.

If there is a non-breaking feature you would like to see implemented in mdl-1.x and are willing to contribute, we'd be happy to offer assistance with you doing so. But we will not personally be actively working on said features.

While we are just getting started with our next version of MDL, you can see our current progress on master as well as an overview of the direction we're headed in our (WIP) developer guide as well as our initial POC branch for our new architecture.

If you're interested in information for a specific MDL v2 component, check out our v2-component issues to see which v2 milestone it's associated with and feel free to subscribe to that issue for updates.

Bugs

Please include the following information with your bug report:

What MDL Version are you using? (please be specific, e.g. major.minor.patch)

What browser(s) is this bug affecting (including version)?

What OS (and version) are you using?

What are the steps to reproduce the bug? Can you create a plunker/codepen/jsfiddle which reproduces it?

What is the expected behavior?

What is the actual behavior?

Any other information you believe would be useful?

@sahilm-10
Copy link

I want to work on this issue. Can you assign it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants