#Development #Techniques
Polishing your typography · The power of the CSS line height units ‘lh’ and ‘rlh’ https://ilo.im/163hyx
_____
#Layout #Typography #LineGrid #LineHight #Text #ProgressiveEnhancement #Browser #WebDev #Frontend #CSS
#progressiveenhancement
0 posts0 participants0 posts today
#Development #Introductions
The customizable select (part two) · Potions, anchoring, and radial shenanigans in CSS https://ilo.im/163bxd
_____
#SelectElement #Form #AnchorPositioning #ProgressiveEnhancement #Chrome #Browser #WebDev #Frontend #HTML #CSS
ilo.imThe customizable select - Part two: Potions, anchoring, and radial shenanigans in CSS | utilitybendThe second part customizable select with CSS series. Highlighting anchor positioning to create a radial potion select element with just HTML and CSS
Targeting an `<iframe>` element is an interesting technique for progressive enhancement (e.g. showing search results in the iframe that updates when the user submits a filter form), however, the lack of feedback for screen readers when the frame navigates makes me think it should be avoided. #ProgressiveEnhancement #accessibility #a11y
#Development #Guidelines
Baseline, more than a rule of thumb? · “Don’t use Google’s Baseline to decide which web features to use.” https://ilo.im/1636ud
_____
#Baseline #Interoperability #Browser #ProgressiveEnhancement #WebDev #Frontend #HTML #CSS #JavaScript #API
Rob O'Leary · Don't use Google's Baseline to decide which web features to useBaseline is a simplified view of browser support. I want to discuss if you should use it to decide which web features to use.
Trying to do a css only proximity hover effect with variable fonts.
I was nearly there and only than understood, that without javascript my variable font is not loading.
aww damn. 
#Development #Releases
CSS scroll-state() · Chrome 133 introduces scroll state container queries https://ilo.im/161umo
_____
#ContainerQueries #Scrolling #ScrollDrivenAnimation #Animation #ProgressiveEnhancement #Chrome #Browser #WebDev #Frontend #CSS
Chrome for DevelopersCSS scroll-state() | Blog | Chrome for DevelopersLike container queries; but for stuck, snapped, and overflowing queries.
Miriam Suzanne – Hints and Suggestions: The Design of Web Design – beyond tellerrand Berlin 2024
https://youtu.be/s2rqYu6jqWY
https://www.ellyloel.com/bookmarks/miriam-suzanne-hints-and-suggestions-the-design-of-web-design-beyond-tellerrand-berlin-2024/
A Framework for Evaluating Browser Support • Josh W. Comeau
https://www.joshwcomeau.com/css/browser-support/ https://www.ellyloel.com/bookmarks/a-framework-for-evaluating-browser-support-josh-w-comeau/
www.joshwcomeau.comA Framework for Evaluating Browser Support • Josh W. ComeauLots of exciting new features have been landing in CSS recently, and it can be tough trying to figure out if they’re safe to use or not. We might know that a feature is available for 92% of users, but is that sufficient? Where do we draw the line? In this blog post, I’ll share the framework I use for deciding whether or not to use a modern CSS feature
Replied in thread
Thank you for stopping to think about this, @AppleJuiceNerd.
The approach that I'd recommend is termed #ProgressiveEnhancement.
Your site should work entirely without #JavaScript, load all the information and render just with HTML and CSS.
Then, if you have enhancements which *require* scripting, add those. If there are relatively-new features you want to use, make sure nothing crucial depends on that new version.
This can be more work, you may have to duplicate a feature or two; be sparing.
Microsoft Mgmt Deteriorates GitHub UX - Goodbye Perf and Progressive Enhancement?
Mu-An Chiou writes @muan:
"React got pushed down from Microsoft management and most of us on the [GitHub] front-end team quit."
Mu-An ChiouJavaScript dos and donts @ Mu-An ChiouDo
When the core functionality of a feature cannot function with only HTML.
When the core functionality of a feature can benefit from some JavaScript. Start with only HTML, then progressively enhance it, so it can still work without Jav...
Replied in thread
@octothorpe @jensimmons If browsers then provided a way in their dev tools to degrade their browsers to the #MinimalViableWeb subset, then we could once again have an easy way to test #ProgressiveEnhancement and #GracefulDegradation, just like we had back when one could expect #InternetExplorer to represent that smallest common denominator among browser implementations
Continued thread
A common piece of feedback I receive on this one is “it’s Chrome-only, so I won’t use it”.
Here’s the kicker: that doesn’t really matter here, as it’s a nice #ProgressiveEnhancement: Browsers without support get the status quo. Browsers with support get the nice transition.
At worst you make the experience better in browsers with support.
https://developer.chrome.com/docs/css-ui/animate-to-height-auto/
Chrome for DevelopersAnimate to height: auto; (and other intrinsic sizing keywords) in CSS | CSS and UI | Chrome for DevelopersAnimate to and from intrinsic sizing keywords with `interpolate-size` and `calc-size()`
Replied in thread
@schizanon@mas.to sort of a philosophical question:
If I'm rendering posts on the client-side, should I remove server-side rendering in order to speed up the initial page load? Currently it sometimes timesout.
This would make the app essentially useless with #JavaScript disabled, which is kind of why I've put this off this long. I'm kind of proud of my No-JS #Mastodon client.
@kristoferjoseph @tbeseda @knowler @colepeters @macdonst @brianleroux @enhance_dev
The problem with our approach to #WebComponents is that we’ve forgotten the “Web” part. It’s really important and it informs what to expect from the “components:” how they work, how we build them, and how they should work with the rest of the Web. Unfortunately, we’ve allowed frameworks built on the premises like “#ProgressiveEnhancement is dead” inform our expectations.
Hello there. #introduction
I'm doing webby things. Originally from Poland, currently based in Berlin. I strongly believe in #progressiveEnhancement, that #accessibility on the web should be inalienable (thought I still have a lot to learn here) and that any single web page should fit on a 1.44MB floppy unless it has a _really_ good reason not to.