Mastodon

46 posts42 participants2 posts today

Frontend DogmaA Progressive Complexity Manifesto, by @cheddybop.bsky.social:<a href="https://www.lorenstew.art/blog/progressive-complexity-manifesto" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.lorenstew.art/blog/progressive-complexity-manifesto</a><a href="https://mas.to/tags/manifestos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#manifestos</a> <a href="https://mas.to/tags/complexity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#complexity</a> <a href="https://mas.to/tags/webapps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#webapps</a> <a href="https://mas.to/tags/html" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#html</a> <a href="https://mas.to/tags/htmx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#htmx</a> <a href="https://mas.to/tags/javascript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#javascript</a> <a href="https://mas.to/tags/webcomponents" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#webcomponents</a> <a href="https://mas.to/tags/frameworks" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#frameworks</a> <a href="https://mas.to/tags/principles" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#principles</a>

Inautilo<a href="https://mastodon.social/tags/Development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Development</a> What to know about modern CSS in 2025 · There is more this year than there was last <a href="https://ilo.im/16711o" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://ilo.im/16711o</a>_____ <a href="https://mastodon.social/tags/ModernCSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ModernCSS</a> <a href="https://mastodon.social/tags/BrowserSupport" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BrowserSupport</a> <a href="https://mastodon.social/tags/ProgressiveEnhancement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ProgressiveEnhancement</a> <a href="https://mastodon.social/tags/Polyfill" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Polyfill</a> <a href="https://mastodon.social/tags/Browser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Browser</a> <a href="https://mastodon.social/tags/WebDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebDev</a> <a href="https://mastodon.social/tags/Frontend" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Frontend</a> <a href="https://mastodon.social/tags/HTML" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HTML</a> <a href="https://mastodon.social/tags/CSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CSS</a> <a href="https://mastodon.social/tags/JavaScript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#JavaScript</a>

Frontend DogmaThe “picture” Element, by <a href="https://front-end.social/@kevinpowell" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@kevinpowell</a>:<a href="https://html-css-tip-of-the-week.netlify.app/tip/the-picture-element/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://html-css-tip-of-the-week.netlify.app/tip/the-picture-element/</a><a href="https://mas.to/tags/html" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#html</a>

Otto RaskWhat is the deal with people using Tailwind CSS or comparable and not being able to add any other class names or IDs to HTML elements other than what the tool offers?I really hate writing browser user styles for Tailwind sites (to fix readability or other issues) because I don't get to use something like `main .aside-left > .meta` to apply styles. Instead I have to build some intricate `main .lg-pad-2.fg-color-3.foobar-md-16 > .bg-color-1.lg-pad-4` to get it done.<a href="https://piipitin.fi/tags/CSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CSS</a> <a href="https://piipitin.fi/tags/HTML" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HTML</a> <a href="https://piipitin.fi/tags/TailwindCSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TailwindCSS</a>

Terence Eden’s BlogClass Warfare! Can I eliminate CSS classes from my HTML?<a href="https://shkspr.mobi/blog/2025/09/class-warfare-can-i-eliminate-css-classes-from-my-html/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://shkspr.mobi/blog/2025/09/class-warfare-can-i-eliminate-css-classes-from-my-html/</a>I recently read a brilliantly provocative blog post called "<a href="https://aaadaaam.com/notes/no-class/" rel="nofollow noopener noreferrer" target="_blank">This website has no class</a>". In it, Adam Stoddard makes the case that you might not need CSS classes on a modern website:<blockquote>I think constraints lead to interesting, creative solutions […]. Instead of relying on built in elements a bit more, I decided to banish classes from my website completely.</blockquote>Long time readers will know that I'm a big fan of using semantic HTML where possible. If you peek beneath the curtain of this website you'll only see a handful of <code><div></code> elements (mostly because WordPress hardcodes them) - all the other blocks are fully semantic. Regrettably, there are rather too many <code></code> elements for my liking - normally for accessibility or for supplementing the metadata.Overall, my CSS contained about 134 rules which selected based on class. Is that a lot? It feels like a lot.On the one hand, classes are an easy way of splitting and grouping elements. Some <code><img></code>s should be displayed one way, the rest another. There's no semantic way to say "This is a hero image and should take up the full width, but this is an icon and should float discretely to the right."But, on the other hand, why do we need classes? Keith Cirkel's excellent post "<a href="https://www.keithcirkel.co.uk/css-classes-considered-harmful/" rel="nofollow noopener noreferrer" target="_blank">CSS Classes considered harmful</a>" goes through their history and brings together some proposed solutions for replacing them. I think his idea of using <code>data-</code> attributes is a neat hack - but ultimately isn't much different from using classes. It's still a scrap of metadata to be tied into a style-sheet.Classes are great for when you reuse something. I have multiple <code><section></code> elements but most don't share anything in common with the others. So they probably oughtn't have classes.Removing classes has some advantages. It makes the HTML fractionally smaller, sure, but it also forces the author to think about the logical structure of their page and the semantics behind it.Looking through my HTML, lots of classes exist because of laziness. If I want to position all the <code><time></code> elements which are within a comment, I don't need to write <code><time class="whatever"></code> and to pair it with <code>.whatever { … }</code>. Instead, I can use modern CSS selectors and say <code>#comments time { … }</code>.But this leads me on to another existential question.Are IDs necessary in modern HTML?Mayyyyybe? I only have one <code><main></code> element, so an ID on there is unnecessary. <code><input></code> elements need IDs in order to be properly targetted by <code><label></code>s - but the label can wrap around the input. I have multiple <code><aside></code> elements because there's no semantic <code><widget></code> element, so they need unique IDs.In theory, as suggested by Adam above, I could use an <a href="https://developer.mozilla.org/en-US/docs/Web/API/Web_components/Using_custom_elements" rel="nofollow noopener noreferrer" target="_blank">autonomous custom element</a> like <code><my-widget></code> - but that has none of the semantics and, frankly, feels like a bit of a cheat.Trimming the fatAny day where I can delete some code is a good day. This was an excellent exercise in going through (years) of HTML and CSS to see what cruft had built up.The first CSS rule I changed was, as mentioned above:<pre><code>time.commentmetadata { float: right;}</code></pre>Which became:<pre><code>#comments time { float: right;}</code></pre>Classless and slightly more brief. Is it more readable? Having the fact it was about the metadata in a class could have been slightly useful - but if I thought it would be confusing, I could stick a <code>/* comment */</code> in there.Next, I found <code><nav class="navigation posts-navigation"></code> - what a tautology! I have multiple <code><nav></code> elements, it is true. But none of them have the same style. So this swiftly became <code><nav id="posts-navigation"></code> with an accompanying CSS rewrite.My theme switcher had a bunch of <code><label class=button></code>s. They were all within a container with a unique ID, so could they be changed? Yes. But seeing the class name in the HTML is a good reminder to the author of how they are meant to display. Does that co-mingle content and presentation too much?Some of the WordPress default classes are ridiculous. The <code>body_class()</code> function injected this into every <code><body></code><code>"wp-singular post-template-default single single-post postid-62959 single-format-standard wp-theme-edent-wordpress-theme"</code>Most of that is redundant - what's the difference between single and single-post? For my purposes, nothing! So they were all yeeted into the sun.Rather than targetting IDs or classes, I targetted the presence or absence of Schema.org microdata.For example:<pre><code>main[itemprop="blogPost"] { … }main:not([itemprop="blogPost"]) { … }</code></pre>This can go to the extreme. I have lots of comments, each one has an author, the author's details are wrapped in <code><div class="authordetails">…</div></code>That can be replaced with:<pre><code>/* Comment Author */li[itemtype="https://schema.org/Comment"] > article > div[itemprop="https://schema.org/author"] { margin-bottom: 0;}</code></pre>Is that sensible? It is more semantic, but feels a bit brittle.Parent selector are also now a thing. If I want a paragraph to have centred text but only when there's a submit button inside it:<pre><code>p:has(input#submit) { text-align: center;}</code></pre>Again, am I sure that my button will always be inside a paragraph?Similarly, <a href="https://css-tricks.com/child-and-sibling-selectors/" rel="nofollow noopener noreferrer" target="_blank">sibling selectors</a> are sometimes superior - but they do suppose that your layout never changes.What remains?There are some bits of this site which are reusable and do need classes. The code-highlighting you see above requires text to be wrapped in spans with specific classes.Image alignment was also heavily class based.There are some accessibility things which are either hidden or exposed using classes.A bunch of WordPress defaults use classes and, even if they are redundant, it's hard to exorcise them.As much as I would have liked to get rid of all my IDs, many needed to stay for linking as well as CSS targetting.All told, the changes I made were:<ul><li>134 class selectors down to about 65.</li><li>35 ID selectors up to about 50.</li><li>5 attribute selectors up to to about 20.</li><li>Deleted or combined a lot of redundant CSS and tidied up my markup considerably.</li></ul>I have around 250 CSS rules, so now the majority target semantics rather than classes or IDs.Is this really necessary?No, of course not. This is an exercise in minimalism, creativity, and constraint. Feel free to litter your HTML with whatever attributes you want!As I went through, it increasingly became apparent that I was fitting my CSS to my HTML's logical structure rather than to its conceptual structure.Previously, my comments were targetted with a class. Now they have the slightly more tangled targetting of "divs with this schema attribute whose parent is an article and whose grandparent has this ID".It is a delightful meditative exercise to go through your code and deeply consider whether something is unique, reusable, or obsolete.<a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://shkspr.mobi/blog/tag/blog/" target="_blank">#blog</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://shkspr.mobi/blog/tag/css/" target="_blank">#css</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://shkspr.mobi/blog/tag/html/" target="_blank">#HTML</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://shkspr.mobi/blog/tag/schema-org/" target="_blank">#schemaOrg</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://shkspr.mobi/blog/tag/semantic-web/" target="_blank">#semanticWeb</a>

Terence Eden🆕 blog! “Class Warfare! Can I eliminate CSS classes from my HTML?”I recently read a brilliantly provocative blog post called "This website has no class". In it, Adam Stoddard makes the case that you might not need CSS classes on a modern website:I think constraints lead to interesting, creative solutions […]. Instead of relying on b…👀 Read more: <a href="https://shkspr.mobi/blog/2025/09/class-warfare-can-i-eliminate-css-classes-from-my-html/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://shkspr.mobi/blog/2025/09/class-warfare-can-i-eliminate-css-classes-from-my-html/</a> ⸻ <a href="https://mastodon.social/tags/blog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#blog</a> <a href="https://mastodon.social/tags/css" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#css</a> <a href="https://mastodon.social/tags/HTML" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HTML</a> <a href="https://mastodon.social/tags/schema" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#schema</a>.org <a href="https://mastodon.social/tags/semanticweb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#semanticweb</a>

CSS by T. Afif :verified:💫 CSS Loaders!Adding 10 new loaders to the collection<a href="https://css-loaders.com/growing/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://css-loaders.com/growing/</a>That makes the total 700 single-element loaders! 👀🥳<a href="https://front-end.social/tags/CSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CSS</a> <a href="https://front-end.social/tags/HTML" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HTML</a>

Matthias Ott🤔 Is there a tool that lets you check the HTML heading levels of a whole website (with all pages) and outputs a list of all pages with problems. Similar to pa11y, but limited to heading levels…? <a href="https://mastodon.social/tags/a11y" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#a11y</a> <a href="https://mastodon.social/tags/html" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#html</a>

Frontend DogmaJust Use HTML, by <a href="https://mastodon.social/@cferdinandi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@cferdinandi</a>:<a href="https://gomakethings.com/just-use-html/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://gomakethings.com/just-use-html/</a><a href="https://mas.to/tags/html" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#html</a> <a href="https://mas.to/tags/javascript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#javascript</a>

HackerNoonDiscover the critical HTML mistakes causing layout bugs, broken characters, and failed social previews. <a href="https://hackernoon.com/6-html-pitfalls-and-gotchas-every-developer-should-avoid" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://hackernoon.com/6-html-pitfalls-and-gotchas-every-developer-should-avoid</a> <a href="https://mas.to/tags/html" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#html</a>

ratfactorHTML WARDen's history view and version diffing feature is probably as complete as it needs to be. (And I'm still under 1k lines, woo!)The, "it's a static website AND live wiki at the same time!" thing I mentioned in the previous toot is next.<a href="https://mastodon.art/tags/php" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#php</a> <a href="https://mastodon.art/tags/wiki" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#wiki</a> <a href="https://mastodon.art/tags/html" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#html</a>

Adrian RoselliVery quick, very dirty testing of voice control with visibly unlabeled fields: <a href="https://cdpn.io/aardrian/debug/MYadEmB" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://cdpn.io/aardrian/debug/MYadEmB</a>The pen itself: <a href="https://codepen.io/aardrian/pen/MYadEmB" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://codepen.io/aardrian/pen/MYadEmB</a>It seems hiding visible labels is a great way to be mean to voice control users.<a href="https://toot.cafe/tags/HTML" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HTML</a> <a href="https://toot.cafe/tags/accessibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#accessibility</a> <a href="https://toot.cafe/tags/a11y" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#a11y</a>

That HTML BlogI cannot sing the praises of fetch loudly enough. As a <a href="https://intuitivefuture.com/tags/JavaScript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#JavaScript</a> <a href="https://intuitivefuture.com/tags/WebDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebDev</a>, having ready access to this native web API where you can pull down <a href="https://intuitivefuture.com/tags/HTML" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HTML</a> fragments or <a href="https://intuitivefuture.com/tags/JSON" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#JSON</a> data with a line or two of code is simply brilliant.But when shipping robust production code, how do you handle unpredictable network scenarios gracefully and provide a good user experience?One solution: a tiny 2.3KB wrapper around “fetch” called “ffetch”. Here are some of its features:<a href="https://thathtml.blog/2025/09/give-fetch-a-bit-more-oomph/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://thathtml.blog/2025/09/give-fetch-a-bit-more-oomph/</a>

Artyom BologovWhat’s worrying me as an <a href="https://merveilles.town/tags/HTML" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HTML</a> extremist is the inevitability of either <a href="https://merveilles.town/tags/JavaScript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#JavaScript</a> or backend:- I can craft beautiful apps that’d work client-side and bring value. But these will require <a href="https://merveilles.town/tags/JS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#JS</a> and will inevitably exclude a fraction of people with JS off or on non-mainstream browsers.- But the alternative to that is having a backend doing the work and sending pre-rendered pages to the user. Which means I have to rent a server somewhere, which to me, a Digital Bum (<a href="https://aartaka.me/digital-bum" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://aartaka.me/digital-bum</a>) is too much of an investment (not monetary, but ideological.)For now, I’m leaning towards client-side JS. Because it means self-contained mini-apps rendered client-side. But it also means progressive enhancement will suffer — no way to utilize HTML forms and backend processing.Chat, anyone aware of a service for (declarative?) mini-backends? No, <a href="https://merveilles.town/tags/CGI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CGI</a> is not an option, because it’s simply dangerous and recless to expose unstructured scripts to the <a href="https://merveilles.town/tags/Web" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Web</a> and I don’t want to inadvertently <a href="https://merveilles.town/tags/DDoS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DDoS</a> my backend provider 😰

Elena. (she/ her)Why not start a blog? Or any other kind of website off of social media? Especially if the social media you're using is not yours (like your own fedi server). Do save your pages/ files/ texts on your computer too, not just on the server your site/ blog lives on, so they don't vanish should the host server vanish. Don't be afraid of shouting into the void at first. Enjoy the process of finding out what you would like to do with your site. People will find you if you want that! Not ready to publish to the world? Play with the site on your computer first. There is no need to ever publish your site anywhere. Use a service that offers pre-existing designs or try your hand at HTML and maybe even CSS yourself. Resources for the latter could be <a href="https://www.htmlforpeople.com/" rel="nofollow noopener noreferrer" target="_blank">HTML for people</a> by <a href="https://social.lol/@bw" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@bw@social.lol</a> <a href="https://neocities.org" rel="nofollow noopener noreferrer" target="_blank">NeoCities</a> those you can find on <a href="https://theresmiling.eu/links#htmlcss" rel="nofollow noopener noreferrer" target="_blank">my site's links collection</a> and many more. Don't worry about a schedule. Post stuff whenever you want. 5 times a day, once every 6 months, or something else entirly - it's your site and your rules. Most of all: Have fun creating, have fun learning, have fun expressing yourself! <a href="https://ibe.social/tags/personalWebsite" rel="nofollow noopener noreferrer" target="_blank">#personalWebsite</a> <a href="https://ibe.social/tags/personalBlog" rel="nofollow noopener noreferrer" target="_blank">#personalBlog</a> <a href="https://ibe.social/tags/html" rel="nofollow noopener noreferrer" target="_blank">#html</a> <a href="https://ibe.social/tags/personalWeb" rel="nofollow noopener noreferrer" target="_blank">#personalWeb</a> <a href="https://ibe.social/tags/indieWeb" rel="nofollow noopener noreferrer" target="_blank">#indieWeb</a> <a href="https://ibe.social/tags/smallWeb" rel="nofollow noopener noreferrer" target="_blank">#smallWeb</a>

Inautilo<a href="https://mastodon.social/tags/Development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Development</a> <a href="https://mastodon.social/tags/Guidelines" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Guidelines</a> CSS to speech · When and how to use alt text for CSS content <a href="https://ilo.im/166yim" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://ilo.im/166yim</a>_____ <a href="https://mastodon.social/tags/CSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CSS</a> <a href="https://mastodon.social/tags/AltText" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AltText</a> <a href="https://mastodon.social/tags/Content" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Content</a> <a href="https://mastodon.social/tags/Images" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Images</a> <a href="https://mastodon.social/tags/Accessibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Accessibility</a> <a href="https://mastodon.social/tags/ScreenReader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ScreenReader</a> <a href="https://mastodon.social/tags/Browser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Browser</a> <a href="https://mastodon.social/tags/WebDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebDev</a> <a href="https://mastodon.social/tags/Frontend" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Frontend</a> <a href="https://mastodon.social/tags/HTML" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HTML</a>

Rena :gay_and_pir:「Angelus Project」Consejos HTML: No subas imágenes de prueba a tu repositorio porque acabará hasta arriba de roña, utiliza <a href="https://picsum.photos/200/300" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://picsum.photos/200/300</a> Cambias el 200 por el ancho y el 300 por el alto, y listo.<a href="https://masto.es/tags/HTML" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HTML</a> <a href="https://masto.es/tags/frontend" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#frontend</a> <a href="https://masto.es/tags/webDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#webDev</a>

Inautilo<a href="https://mastodon.social/tags/Development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Development</a> <a href="https://mastodon.social/tags/Previews" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Previews</a> CSS :heading and :heading() · Styling headings is about to get much easier <a href="https://ilo.im/166xa6" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://ilo.im/166xa6</a>_____ <a href="https://mastodon.social/tags/ModernCSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ModernCSS</a> <a href="https://mastodon.social/tags/Styling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Styling</a> <a href="https://mastodon.social/tags/Headings" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Headings</a> <a href="https://mastodon.social/tags/Firefox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Firefox</a> <a href="https://mastodon.social/tags/Browser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Browser</a> <a href="https://mastodon.social/tags/WebDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebDev</a> <a href="https://mastodon.social/tags/Frontend" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Frontend</a> <a href="https://mastodon.social/tags/HTML" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HTML</a> <a href="https://mastodon.social/tags/CSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CSS</a>

FreeSchool=Co-Op+Friendship🔁?<a href="https://phpc.social/@davidbisset" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@davidbisset</a> <a href="https://qoto.org/tags/Mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mastodon</a> <a href="https://qoto.org/tags/Backup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Backup</a> <a href="https://qoto.org/tags/Archive" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Archive</a> <a href="https://qoto.org/tags/Viewer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Viewer</a> <a href="https://qoto.org/tags/Converter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Converter</a> <a href="https://qoto.org/tags/Search" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Search</a> <a href="https://qoto.org/tags/Posts" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Posts</a> <a href="https://qoto.org/tags/Offline" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Offline</a> <a href="https://qoto.org/tags/Export" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Export</a> <a href="https://qoto.org/tags/Archives" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Archives</a> <a href="https://qoto.org/tags/Static" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Static</a> <a href="https://qoto.org/tags/HTML" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HTML</a> Has anyone tested this further ? ☑️ :blackcat: I've tested <a href="https://qoto.org/tags/MeowViewer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MeowViewer</a> which works very well by <a href="https://toot.cafe/@meowViewer" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@meowViewer</a> who is developing it ⭐ <a href="https://qoto.org/tags/MeowViewer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MeowViewer</a> = Fast, local, can view offline (needs online to start) Would be great if it could be run as standalone offline version - but after online upload you can even search you own posts which can hit hit and miss standard search bar or sometimes doesn't work to find much!)

Terence EdenA little accessibility question, if you have the time, inclination, and experience to answer.Informative images should have alt text.Decorative images should have null alt text.Null text is usually written as: alt=""But attributes don't *need* values.So, do screen readers treat these two images in the same way?<img alt="" src="example.jpg"> <img alt src="example.jpg">That is, can I leave out the ="" on my alt attribute for decorative images?<a href="https://mastodon.social/tags/A11y" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#A11y</a> <a href="https://mastodon.social/tags/Accessibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Accessibility</a> <a href="https://mastodon.social/tags/HTML" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HTML</a>

Recent searches

Search options

Administered by:

Server stats:

#html