#progressiveenhancent — Public Fediverse posts

Pretty cool how simple it is to strap in #viewtransition with #HTMX without any fuzz and completely in the spirit of #progressiveenhancent ❤️

I’ll definitely strap this in and be ready for browser compatibility to get there 😊

https://khalidabuhakmeh.com/view-transitions-api-with-aspnet-core-and-htmx

Pretty cool how simple it is to strap in #viewtransition with #HTMX without any fuzz and completely in the spirit of #progressiveenhancent ❤️

I’ll definitely strap this in and be ready for browser compatibility to get there 😊

https://khalidabuhakmeh.com/view-transitions-api-with-aspnet-core-and-htmx

Pretty cool how simple it is to strap in #viewtransition with #HTMX without any fuzz and completely in the spirit of #progressiveenhancent ❤️

I’ll definitely strap this in and be ready for browser compatibility to get there 😊

https://khalidabuhakmeh.com/view-transitions-api-with-aspnet-core-and-htmx

Pretty cool how simple it is to strap in #viewtransition with #HTMX without any fuzz and completely in the spirit of #progressiveenhancent ❤️

I’ll definitely strap this in and be ready for browser compatibility to get there 😊

https://khalidabuhakmeh.com/view-transitions-api-with-aspnet-core-and-htmx

Curious if there are #ProgressiveEnhancent approaches people are using to recent #CSS features like cascade layers, nesting and proposed ones like scope.

I get that older browsers will just ignore @ rules they don't support and you can probably feature detect some of this via supports.

But, these aren't new properties for adding some optional visual flourish. These fundamentally alter how you organise your CSS code.

I struggle to see how one might use them in a way that there's enough...

Curious if there are #ProgressiveEnhancent approaches people are using to recent #CSS features like cascade layers, nesting and proposed ones like scope.

I get that older browsers will just ignore @ rules they don't support and you can probably feature detect some of this via supports.

But, these aren't new properties for adding some optional visual flourish. These fundamentally alter how you organise your CSS code.

I struggle to see how one might use them in a way that there's enough...

Curious if there are #ProgressiveEnhancent approaches people are using to recent #CSS features like cascade layers, nesting and proposed ones like scope.

I get that older browsers will just ignore @ rules they don't support and you can probably feature detect some of this via supports.

But, these aren't new properties for adding some optional visual flourish. These fundamentally alter how you organise your CSS code.

I struggle to see how one might use them in a way that there's enough...

Curious if there are #ProgressiveEnhancent approaches people are using to recent #CSS features like cascade layers, nesting and proposed ones like scope.

I get that older browsers will just ignore @ rules they don't support and you can probably feature detect some of this via supports.

But, these aren't new properties for adding some optional visual flourish. These fundamentally alter how you organise your CSS code.

I struggle to see how one might use them in a way that there's enough...

Curious if there are #ProgressiveEnhancent approaches people are using to recent #CSS features like cascade layers, nesting and proposed ones like scope.

I get that older browsers will just ignore @ rules they don't support and you can probably feature detect some of this via supports.

But, these aren't new properties for adding some optional visual flourish. These fundamentally alter how you organise your CSS code.

I struggle to see how one might use them in a way that there's enough...