Gaël Poupard

[Feature] Specify `manifest.json` path

4

Reviving #1034. Currently working on a manifest V2 → V3 migration, separate manifest files are needed for Firefox and Chromium based browsers: - `background` entry needs a `service_worker` string for...

Charts and data vizualisation

3

Hi there! Back to RTL topic, I'm currently implementing RTL in [chaarts](https://github.com/ffoodd/chaarts/pull/106) and decided for some kind of charts to not flip them. Here're my thoughts: - for circular charts...

[Fly-out] — Hit areas using `clip-path`

2

Inspired by @hakimel's [demonstration video on Twitter](https://twitter.com/hakimel/status/1132932935399673857), I think we could improve the hit area using pure CSS :) And keep progressive enhancement in mind, obviously

Typographic scale

5

Using a single custom properties to handle *ratio*, we could handle the whoel typographic scale with `calc()`. See [modularscale.com](https://www.modularscale.com/).

Use custom properties to handle components' variants

1

By using custom properties, we may ease contextual variants for components. An example: sizing a component in `em` would be muc, much easier with things like `font-size: calc( 1em *...

Based on everylayout.dev and checking smol or other ressources.

Would be nice to handle base styles for `iframe` beyond normalization: could be really fun to display a browser tab around, with navigation bar showing URL and title, and OS...

There's a lot to try here: * read the [Content Slider post on Inclusive Components](https://inclusive-components.design/a-content-slider/) by @Heydon; * more about [CSS s croll snap point on MDN](https://developer.mozilla.org/fr/docs/Web/CSS/CSS_Scroll_Snap_Points); * also a...

Finally, styling SVGs inlined through `` can be a thing thanks to custom properties: - https://codepen.io/petebarr/pen/oNjLebr - https://filamentgroup.netlify.app/images/includespost/customizesvgembed.html