materialdesignweb
csswg-drafts
materialdesignweb | csswg-drafts | |
---|---|---|
17 | 70 | |
37 | 4,278 | |
- | 0.6% | |
9.3 | 9.9 | |
23 days ago | 1 day ago | |
JavaScript | Bikeshed | |
ISC License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
materialdesignweb
- The future of Sync
- I made flappy bird with pure HTML CSS JavaScript
-
What problem does Virtual DOM solve for React?
I wanted something that didn't require recompilation and allows me to extend built components. Like an Chip extends a Button. I needed something that allows modification of its HTML template and layering of CSS styles on top of an extended element's styles. Frameworks are pretty rigid in this regard and I wanted to write less code to make a smaller final deployment, instead of copy pasting or having to write complicated mixins and abstractions.
-
Material You in Android 14 getting ‘personal’ with bolder ‘Fidelity’ colors
My phone is basically grayscale expect for really minor blue hue. I'm not sure why, and I know how the Material You theming works (built a framework around it).
-
Lighthouse doesn't like Shadow DOM...
For the curious: Test page - Source Code
- Lighthouse doesn't like Shadow DOMs...
-
Would it be possible to build such a bar with CSS? The hardest part looks like the curved piece of bar under the blue button.
Source: https://github.com/clshortfuse/materialdesignweb/tree/archive-md2/components
-
Anyone ever experienced any physical repulsion to Material Design after using Apple devices?
If you're tired of it, I've been maintaining my MD framework for more than 4 and a half years since 2018. And before that I was working with Google on the AngularJS implementation in 2015. So I've been looking at and working on the same styles for over 7 years.
-
[AskJS] What is an issue you struggle with your current tech stack?
Here is the JS for one of the components. Only Chrome natively understands it right now. The alternative is to use a element referencing the CSS, but will call FOUC on the first fetch.
-
Prevent button focus on long press
Code
csswg-drafts
-
Help us invent CSS Grid Level 3, a.k.a. "Masonry" layout – WebKit
For more background, and some detailed discussion of the opposite argument ("display: masonry" over "display:grid"+"grid-template-rows: masonry") see https://github.com/w3c/csswg-drafts/issues/9041
-
Chrome Dev: High Definition CSS Color Guide
The tracking issue: https://github.com/w3c/csswg-drafts/issues/8659
As noted there, okHSL/HSV keeps the perceptual uniformity by removing some peaks beyond the geometric limit of HSL/HSV, and it is unclear whether it is what users do expect or not.
-
Announcing Winduum 1.0 - Framework agnostic component library for TailwindCSS
The idea is that you should be able to set accent color via accent-color CSS property. It is discussed that there should be access to the color value of this property, e.g. via AccentColor or AccentColorText.
-
Learn CSS Layout the Pedantic Way
What do you mean by "official documentation"? The specification [1]? MDN [2]?
[1] https://drafts.csswg.org/
[2] https://developer.mozilla.org/en-US/docs/Web/CSS
The former is not meant as a learning resource for new web devs and the latter usually has information about the "baseline" support ond browser compatibility tables.
-
CSS WG resolved to officially work on native custom functions and mixins
The link corresponding to the actual submission title (“CSS WG resolved to officially work on native custom functions and mixins”):
https://github.com/w3c/csswg-drafts/issues/9350#issuecomment...
> RESOLVED: Start ED of css-mixins for CSS Custom Functions and Mixins
-
Weird things engineers believe about Web development
Recently I was reading the Learn CSS the pedantic way book and the definition for inline boxes did not match the way that anonymous block boxes were generated when an inline-level element had a block-level element as its child. So I went looking elsewhere for a more appropriate definition for that case and found this issue on standards: https://github.com/w3c/csswg-drafts/issues/1477 It was really interesting to know that I was not the only one confused. My question was: Does the inline-box generated by the inline-level element contains the box generated by the block-level child or there wasn't an inline-box that was a parent of them all but there were 2 siblings inline-level boxes of the block-level box that were wrapped in another anonymous block boxes? Reading that issue I got to know the concept of fragments, which I did not know browsers had. But the issue seems to suggest that the box tree for this case should have the inline-box as being a parent of the block-box. Which led me to another question, in that case, if I apply a border to the parent inline-level element, shouldn't it apply to the overall box that is generated (it does not)? The answer is that borders between block-boxes and inline-level boxes should not intersect but that is really difficult to derive from reading the standards alone. Anyway it was headache-inducing trying to learn the box-model pedantically :)
-
CSS Is Fun Again
With all the recent CSS improvements I still miss the possibility to have working transition to "height:auto". The issue [1] on csswg-drafts is the most upvoted one. At least we can now use css grid and track sizes transitions, but it's far from intuitive, transition for "height:auto" should just work.
[1]: https://github.com/w3c/csswg-drafts/issues/626
- Proposed "au" unit for CSS provides for styling on an astronomical scale
-
The Future of CSS: Easy Light-Dark Mode Color Switching with Light-Dark()
Masonry isn’t ready to be shipped as there are still quite a few open spec issues [^1] that need to be resolved first.
[^1]: https://github.com/w3c/csswg-drafts/issues?q=is%3Aissue+is%3...
-
CSS Solves Auto-Expanding Textareas
the irc log is here: https://github.com/w3c/csswg-drafts/issues/7542#issuecomment...
i had the same reaction, it seems like a very weird syntax. but after reading the discussion i get it: you're telling a form field to behave like a normal html element, instead of behaving like a form field.
What are some alternatives?
old-reddit-redirect - Ensure Reddit always loads the old design
Modernizr - Modernizr is a JavaScript library that detects HTML5 and CSS3 features in the user’s browser.
buttplug-rs - Rust Implementation of the Buttplug Sex Toy Control Protocol
open-props - CSS custom properties to help accelerate adaptive and consistent design.
Flickity - :leaves: Touch, responsive, flickable carousels
WHATWG HTML Standard - HTML Standard
cordova-plugin-health - Cordova plugin for the HealthKit and Google Fit frameworks
Rotativa - Rotativa, /rota'tiva/. Make Pdf from Asp.Net MVC. Available on Nuget https://www.nuget.org/packages/Rotativa
lit - Lit is a simple library for building fast, lightweight web components.
rellax - Lightweight, vanilla javascript parallax library
proposals - Tracking WebAssembly proposals
container-query-polyfill - A polyfill for CSS Container Queries