If there was an #HTML element that changes it's content when users interact with other elements on the page, what name would it have?
PLEASE NOTE: I am not suggesting that this element needs to exist; I am only asking what it would be called. I'm building a CustomElement, I just want it to have a name that makes sense.
Vote and suggest others in replies. Please boost for reach!
What are your top #CSS features you played with, got excited over as they were supported in one browser... then years passed & support hasn't improved?
Mine:
✨@property Chrome-only for half a decade
✨filter() Safari-only since 2015
✨element() Firefox-only since forever
Now that Safari 17.4 is available, what other new web technology — HTML, CSS, JS, Web API, media support, etc — would you like to see supported in Safari next?
What’s most needed?
What will you use it for?
Or how will it help your team serve your users?
Tell me a story…
One thing I will say: Rust on the web is overkill. I know, it's tempting to have something like leptos and have a single language on both frontend and backend.
What you should be doing is using the web platform. Most work should be done on the server anyways, your front end code should only be used for progressive enhancement. The user shouldn't have to run JavaScript in order to use your site. Plain and simple.
This presentation covers how I transformed my website from being a static digital portfolio into a dynamic hub, ingrained with my social presence, containing the most authentic version of me online.
CSS has a containment property whichs sole purpose is to improve rendering performance.
So, first, we develop an abstraction so developers don't have to worry about implementation details like performance. Then, as soon as we realise that our abstractions are (obviously) dog slow, we add more stuff to make them fast again and have developers worry about that instead.
At this point, we might as well ship websites as compiled binaries.
1/4
When it comes to web dev, I'm a huge fan of finding simple solutions that leverage fundamental web technologies.
Here are two excellent articles I've stumbled across recently, one explaining 5 new CSS properties and the other about structuring vanilla JavaScript, both very much highlighting some great web fundamentals.
Coincidentally, both were written by a Chris that I admire so that's neat.
Based on my experiences in various frontend codebases that were written without a frontend expert on the team (including my own old projects 💩), I compiled a list of 9 most common signs of frontend code quality issues that affect users https://angelika.me/2024/04/13/9-signs-your-frontend-code-has-quality-issues/
Do you want to add a "log in with your fediverse account" functionality to your site? I am working on a self-hosted node.js server that lets you do just that.
I believe people on the #Fediverse are more likely to add alternative text to the images they post than on any other popular social media platform, that's great for #Accessibility. But it isn't the end-all-be-all of it. For example, when one of my contacts posts in German or Finnish or Farsi, I can copy the text and plug it in a translator to figure out what they meant.
However, when they share a picture including text in the same language, even if they transcribed the text in the picture in the alternative text attribute, I can't access it on mobile at all, and even on desktop I can't copy it from the default popup on mouse hover.
I tried to dabble with #CSS to reveal the alt-text attribute value using pseudo-content, but it doesn't work since we're dealing with an #HTML<img> which is an empty element by definition. Is there any other way to expose this attribute value other than just parse the text in the post body directly?