Csswg-drafts Alternatives

csswg-drafts reviews and mentions

• Blitz: A lightweight, modular, extensible web renderer
  9 projects | news.ycombinator.com | 11 Aug 2024

  > Perhaps the authors can find inspiration by looking at CSS houdini, which tries to make CSS extensible

  Pluggable layout algorithms are definitely something I'd like to enable in Blitz. I suspect JS for layout will be too slow in most cases. But this is an area in which we have an advantage with our API being in Rust. And our layout engine Taffy (https://github.com/DioxusLabs/taffy) is already highly modular.

  Custom widgets would go beyond just layout and allow for fully custom layout, paint, accessibility, event handling, etc similar to a widget in a traditional GUI toolkit like GTK or Cocoa.

  I also have a proposal to add a new unit to CSS itself (inspired by how many non-web UI systems do layout), which has the potential to greatly simplify web layout in the common cases https://github.com/w3c/csswg-drafts/issues/8267. It's been on the back burner for a bit, but I should really get back to it at some point (I really want to actually implement the algorithms).

• Atomic CSS Deep Dive
  10 projects | dev.to | 9 Aug 2024
• Inline if() in CSS 🤔: What You Need to Know About This Upcoming Feature
  1 project | dev.to | 1 Jul 2024

  Lets see how this will work ( according to the proposal ):

• Why is Everyone into Indie Development? - FAV0 Weekly Issue 004
  5 projects | dev.to | 23 Jun 2024

  Github Issues Discussion

• Help us invent CSS Grid Level 3, a.k.a. "Masonry" layout – WebKit
  5 projects | news.ycombinator.com | 23 Apr 2024

  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
  1 project | news.ycombinator.com | 7 Apr 2024

  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
  5 projects | dev.to | 29 Feb 2024

  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
  7 projects | news.ycombinator.com | 27 Feb 2024

  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
  1 project | news.ycombinator.com | 13 Feb 2024

  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
  2 projects | news.ycombinator.com | 7 Jan 2024

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

• A note from our sponsor - SaaSHub
  www.saashub.com | 18 Jan 2025

  SaaSHub helps you find the best software and product alternatives Learn more →