PPC Land<p>W3C streamlines web standards process with major document updates: W3C removes Proposed Recommendation phase and introduces Charter Refinement to simplify standards development while maintaining quality controls. <a href="https://ppc.land/w3c-streamlines-web-standards-process-with-major-document-updates/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">ppc.land/w3c-streamlines-web-s</span><span class="invisible">tandards-process-with-major-document-updates/</span></a> <a href="https://mastodon.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://mastodon.social/tags/W3C" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>W3C</span></a> <a href="https://mastodon.social/tags/TechUpdates" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechUpdates</span></a> <a href="https://mastodon.social/tags/StandardsDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>StandardsDevelopment</span></a> <a href="https://mastodon.social/tags/CharterRefinement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CharterRefinement</span></a></p>
veganism.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Veganism Social is a welcoming space on the internet for vegans to connect and engage with the broader decentralized social media community.
Administered by:
Server stats:
288active users
veganism.social: About · Status · Profiles directory · Privacy policy
Mastodon: About · Get the app · Keyboard shortcuts · View source code · v4.4.0-alpha.5
#WebStandards
4 posts · 3 participants · 0 posts today
Inautilo<p><a href="https://mastodon.social/tags/Development" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Development</span></a> <a href="https://mastodon.social/tags/Debates" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Debates</span></a><br>XSLT is still important · Why we shouldn’t remove it from the web platform <a href="https://ilo.im/165z0w" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">ilo.im/165z0w</span><span class="invisible"></span></a></p><p>_____<br><a href="https://mastodon.social/tags/Styling" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Styling</span></a> <a href="https://mastodon.social/tags/RSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RSS</span></a> <a href="https://mastodon.social/tags/XSLT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XSLT</span></a> <a href="https://mastodon.social/tags/IndieWeb" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IndieWeb</span></a> <a href="https://mastodon.social/tags/SmallWeb" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SmallWeb</span></a> <a href="https://mastodon.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://mastodon.social/tags/WebPlatform" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebPlatform</span></a> <a href="https://mastodon.social/tags/Browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Browser</span></a> <a href="https://mastodon.social/tags/WebDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebDev</span></a> <a href="https://mastodon.social/tags/Frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Frontend</span></a></p>
Otto Rask<p>Google started a WHATWG discussion for removing XSLT. Google has done their best to remove good tech from standards many times.</p><p>Responders raised issue with the motive for this change, as opposed to upgrading from XSLT 1.x to 3.1 which would fix all sorts of issues, etc.</p><p>Any posts that brought up Google's history and motives were marked as off-topic, and the thread was eventually locked by WHATWG.</p><p><a href="https://github.com/whatwg/html/issues/11523" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/whatwg/html/issues/</span><span class="invisible">11523</span></a></p><p><a href="https://piipitin.fi/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://piipitin.fi/tags/OpenWeb" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenWeb</span></a> <a href="https://piipitin.fi/tags/XML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XML</span></a> <a href="https://piipitin.fi/tags/RSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RSS</span></a> <a href="https://piipitin.fi/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Google</span></a> <a href="https://piipitin.fi/tags/Web" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Web</span></a> <a href="https://piipitin.fi/tags/Internet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Internet</span></a> <a href="https://piipitin.fi/tags/WHATWG" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WHATWG</span></a> <a href="https://piipitin.fi/tags/XSLT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XSLT</span></a></p>
Inautilo<p><a href="https://mastodon.social/tags/Development" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Development</span></a> <a href="https://mastodon.social/tags/Analyses" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Analyses</span></a><br>Thoughts on the state of surveys · Biases and barriers in recent State of ___ surveys <a href="https://ilo.im/16653d" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">ilo.im/16653d</span><span class="invisible"></span></a></p><p>_____<br><a href="https://mastodon.social/tags/Surveys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Surveys</span></a> <a href="https://mastodon.social/tags/Biases" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Biases</span></a> <a href="https://mastodon.social/tags/Barriers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Barriers</span></a> <a href="https://mastodon.social/tags/Accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Accessibility</span></a> <a href="https://mastodon.social/tags/Usability" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Usability</span></a> <a href="https://mastodon.social/tags/Browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Browser</span></a> <a href="https://mastodon.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://mastodon.social/tags/WebDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebDev</span></a> <a href="https://mastodon.social/tags/Frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Frontend</span></a></p>
Steve Faulkner<p>👁️ Set heading level based on HTML computed heading level - <span class="h-card" translate="no"><a href="https://indieweb.social/@keithamus" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>keithamus</span></a></span> </p><p><a href="https://mastodon.social/tags/HTML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTML</span></a> <a href="https://mastodon.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://mastodon.social/tags/a11y" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>a11y</span></a></p><p><a href="https://github.com/w3c/aria/pull/2598" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">github.com/w3c/aria/pull/2598</span><span class="invisible"></span></a></p>
Chris Alemany<p>You can see all the videos that have been uploaded so far on the <a href="https://socialbc.ca/tags/fedicon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fedicon</span></a> page here at spectra.video. <a href="https://socialbc.ca/tags/peertube" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>peertube</span></a></p><p><a href="https://spectra.video/c/fedicon_videos/videos" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">spectra.video/c/fedicon_videos</span><span class="invisible">/videos</span></a></p><p> <a href="https://socialbc.ca/tags/fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fediverse</span></a> <a href="https://socialbc.ca/tags/mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mastodon</span></a> <a href="https://socialbc.ca/tags/socialbc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>socialbc</span></a> <a href="https://socialbc.ca/tags/democracy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>democracy</span></a> <a href="https://socialbc.ca/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webstandards</span></a> <a href="https://socialbc.ca/tags/activitypub" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>activitypub</span></a> <a href="https://socialbc.ca/tags/community" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>community</span></a></p>
Chris Alemany<p>If you are interested in how the Fediverse really works and some of the key people making it happen, sit down with a coffee and check out one (or all!) of the presentations from <a href="https://socialbc.ca/tags/fedicon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fedicon</span></a>.</p><p>Mine was about my journey finding the Fediverse and eventually teaming up with folks to create socialbc.ca and what I learned along the way.</p><p>And yes, I am pretty sure we are in a Stanley Kubrick movie.<br><a href="https://socialbc.ca/tags/fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fediverse</span></a> <a href="https://socialbc.ca/tags/mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mastodon</span></a> <a href="https://socialbc.ca/tags/socialbc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>socialbc</span></a> <a href="https://socialbc.ca/tags/democracy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>democracy</span></a> <a href="https://socialbc.ca/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webstandards</span></a> <a href="https://socialbc.ca/tags/activitypub" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>activitypub</span></a> <a href="https://socialbc.ca/tags/community" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>community</span></a> <br><a href="https://spectra.video/w/p9nScG9XFX81iE89ufmWUM" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">spectra.video/w/p9nScG9XFX81iE</span><span class="invisible">89ufmWUM</span></a></p>
dokieli<p>🎉 Good news everyone!</p><p>We are extremely thankful and excited to be supported once again by <span class="h-card" translate="no"><a href="https://social.nlnet.nl/@nlnet" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>nlnet</span></a></span> to work on our roadmap ( <a href="https://dokie.li/docs#roadmap" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">dokie.li/docs#roadmap</span><span class="invisible"></span></a> ) as part of NGI Zero Commons Fund.</p><p>Read the announcement:</p><p><a href="https://nlnet.nl/news/2025/20250804-announcement-grants-CommonsFund.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">nlnet.nl/news/2025/20250804-an</span><span class="invisible">nouncement-grants-CommonsFund.html</span></a></p><p>The project:</p><p><a href="https://nlnet.nl/project/Dokieli-Collaborative/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">nlnet.nl/project/Dokieli-Colla</span><span class="invisible">borative/</span></a></p><p>This time we will focus on these tasks:</p><p>* End-to-end encryption<br>* Collaborative editing<br>* Code modularization<br>* Internationalization<br>* Browser extension improvements</p><p><a href="https://w3c.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a> <a href="https://w3c.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://w3c.social/tags/i18n" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>i18n</span></a> <a href="https://w3c.social/tags/e2ee" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>e2ee</span></a></p>
DoctorG ♀️🏳️🌈<p>How to hide HTML element A from ScreenReader but let i be accessible to keyboard users?</p><p>Tools to check <a href="https://social.vivaldi.net/tags/Accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Accessibility</span></a> nag me, telling it is not allowed to use HTML like this:</p><p><a href="/" aria-hidden="true">Read more…</a></p><p>Solvable problem?</p><p><a href="https://social.vivaldi.net/tags/FollowerPower" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FollowerPower</span></a> <a href="https://social.vivaldi.net/tags/Accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Accessibility</span></a> <a href="https://social.vivaldi.net/tags/ARIA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ARIA</span></a> <a href="https://social.vivaldi.net/tags/WAI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WAI</span></a> <a href="https://social.vivaldi.net/tags/HTML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTML</span></a> <a href="https://social.vivaldi.net/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://social.vivaldi.net/tags/ScreenReader" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ScreenReader</span></a></p>
Tantek Çelik<p>The Vision for W3C has been officially published as a ratified W3C Statement: <a class="" href="https://www.w3.org/TR/2025/STMT-w3c-vision-20250729/" rel="nofollow noopener" target="_blank">https://www.w3.org/TR/2025/STMT-w3c-vision-20250729/</a><br><br>As one of the editors, along with Chris Wilson (<a class="" href="https://cwilso.com" rel="nofollow noopener" target="_blank">@cwilso.com</a> <a class="" href="https://w3c.social/@c" rel="nofollow noopener" target="_blank">@c@w3c.social</a>), I’m both proud of this multi-year W3C Advisory Board (AB) effort, and grateful to everyone who contributed and gave feedback that helped improve the document.<br><br>Writing down and openly publishing our collective values and principles is an important step forward for W3C. We now have a shared reference to both guide our priorities and cite to help resolve differences in opinion (rather than having to appeal to authority).<br><br>The AB (<a class="" href="https://w3.org/wiki/AB" rel="nofollow noopener" target="_blank">@w3.org/wiki/AB</a> <a class="" href="https://w3c.social/@ab" rel="nofollow noopener" target="_blank">@ab@w3c.social</a>) has prioritized work on the Vision project for many years (<a class="" href="https://www.w3.org/wiki/AB/Vision" rel="nofollow noopener" target="_blank">https://www.w3.org/wiki/AB/Vision</a>), and personally, co-leading this project during my time on the AB has been inspiring, challenging, and a source of many lessons learned. Lots more to share on all that. For now, happy to take a moment to celebrate this milestone.<br><br><a class="" href="https://indieweb.social/tags/w3cVision" rel="nofollow noopener" target="_blank">#<span class="p-category">w3cVision</span></a> <a class="" href="https://indieweb.social/tags/VisionForW3C" rel="nofollow noopener" target="_blank">#<span class="p-category">VisionForW3C</span></a> <a class="" href="https://indieweb.social/tags/WorldWideWeb" rel="nofollow noopener" target="_blank">#<span class="p-category">WorldWideWeb</span></a> <a class="" href="https://indieweb.social/tags/W3C" rel="nofollow noopener" target="_blank">#<span class="p-category">W3C</span></a> (<a class="" href="https://w3.org" rel="nofollow noopener" target="_blank">@w3.org</a> <a class="" href="https://w3c.social/@w3c" rel="nofollow noopener" target="_blank">@w3c@w3c.social</a>)<br><a class="" href="https://indieweb.social/tags/openWeb" rel="nofollow noopener" target="_blank">#<span class="p-category">openWeb</span></a> <a class="" href="https://indieweb.social/tags/webStandards" rel="nofollow noopener" target="_blank">#<span class="p-category">webStandards</span></a><br><br>More posts:<br>* <a class="" href="https://www.w3.org/news/2025/vision-for-w3c-is-a-w3c-statement/" rel="nofollow noopener" target="_blank">https://www.w3.org/news/2025/vision-for-w3c-is-a-w3c-statement/</a><br>* <a class="" href="https://www.w3.org/blog/2025/vision-for-w3c-a-manifesto-for-our-operations-and-decision-making/" rel="nofollow noopener" target="_blank">https://www.w3.org/blog/2025/vision-for-w3c-a-manifesto-for-our-operations-and-decision-making/</a></p>
nemo™ 🇺🇦<p>🚨 Advocacy group Movement for an Open Web (MOW) files complaint with UK CMA against W3C's push to kill third-party cookies 🍪❌, accusing it of favoring Google and harming smaller publishers ⚖️📉 <a href="https://mas.to/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://mas.to/tags/Privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Privacy</span></a> <a href="https://mas.to/tags/TechCompetition" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechCompetition</span></a> <a href="https://mas.to/tags/W3C" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>W3C</span></a> <a href="https://mas.to/tags/Cookies" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Cookies</span></a> <a href="https://mas.to/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Google</span></a> <a href="https://www.theregister.com/2025/07/29/mow_w3c_cookie_complaint/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">theregister.com/2025/07/29/mow</span><span class="invisible">_w3c_cookie_complaint/</span></a><br><a href="https://mas.to/tags/newz" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>newz</span></a></p>
Andrew Mark McCall<p>newsflash: html audio element is good enough we don't need your shitty custom implementation that only works in chrome.</p><p><a href="https://indieweb.social/tags/html" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>html</span></a> <a href="https://indieweb.social/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>javascript</span></a> <a href="https://indieweb.social/tags/audio" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>audio</span></a> <a href="https://indieweb.social/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webstandards</span></a></p>
Alda Vigdís<p>And here I am with a spicy take on the <hgroup> HTML element of all things.</p><p>Is the <hgroup> element redundant and should we handle headings and subheadings differently instead of re-introducing the element?</p><p><a href="https://aldavigdis.dev/2025/07/25/taming-html-headings-subheadings-and-overlines/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">aldavigdis.dev/2025/07/25/tami</span><span class="invisible">ng-html-headings-subheadings-and-overlines/</span></a></p><p><a href="https://topspicy.social/tags/WebDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebDev</span></a> <a href="https://topspicy.social/tags/HTML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTML</span></a> <a href="https://topspicy.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a></p>
Julie Blanc<p>📘 Just published: “Designing with Abstractions: CSS and the Case of Masonry Layouts”</p><p>This (academic) article explores CSS as both a technical system and a design object. It examines how this is shaped through negotiation between conceptual models, implementation constraints, and interface considerations, focusing on the Masonry layout debates.</p><p>Appreciation to those participating in CSS WG debates and making this work visible.</p><p>→ <a href="https://journal.dampress.org/issues/design-et-abstractions/designing-with-abstractions-css-and-the-case-of-masonry-layouts" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">journal.dampress.org/issues/de</span><span class="invisible">sign-et-abstractions/designing-with-abstractions-css-and-the-case-of-masonry-layouts</span></a></p><p> <a href="https://mastodon.design/tags/CSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CSS</span></a> <a href="https://mastodon.design/tags/CSSWG" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CSSWG</span></a> <a href="https://mastodon.design/tags/w3c" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>w3c</span></a> <a href="https://mastodon.design/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a></p>
🧿🪬🍄🌈🎮💻🚲🥓🎃💀🏴🛻🇺🇸<p>> <a href="https://mastodon.social/tags/Firefox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Firefox</span></a> has long lagged behind <a href="https://mastodon.social/tags/Chrome" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Chrome</span></a> in adopting new <a href="https://mastodon.social/tags/webStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webStandards</span></a>, but loyal users now have something to celebrate as the <a href="https://mastodon.social/tags/browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>browser</span></a> is finally getting a feature Chrome has offered for years.</p><p><a href="https://www.neowin.net/news/better-late-than-never-firefox-is-finally-getting-a-feature-chrome-users-have-had-for-years/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">neowin.net/news/better-late-th</span><span class="invisible">an-never-firefox-is-finally-getting-a-feature-chrome-users-have-had-for-years/</span></a></p><p><a href="https://mastodon.social/tags/webGPU" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webGPU</span></a> <a href="https://mastodon.social/tags/webDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webDev</span></a> <a href="https://mastodon.social/tags/browsers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>browsers</span></a> <a href="https://mastodon.social/tags/mozilla" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mozilla</span></a></p>
Timo Tijhof<p>When applying a thick border around an element in multiple colors, the corners meet at a 45-degree angle forming a diamond. That is established and seems reasonable.</p><p>But, when you set a thick edge on one side, the thin 1px border gets squeezed into a slope, and won't reach the edge! And the sidebar forms a *trapezoid*!</p><p>This is most noticable on modern high-DPI screens. It is rather unsatisfying, and hard to unsee...</p><p>Example:<br><a href="https://en.wikipedia.org/wiki/Template:Cleanup" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">en.wikipedia.org/wiki/Template</span><span class="invisible">:Cleanup</span></a></p><p><a href="https://fosstodon.org/tags/css" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>css</span></a> <a href="https://fosstodon.org/tags/WebDesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebDesign</span></a> <a href="https://fosstodon.org/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://fosstodon.org/tags/mathstodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mathstodon</span></a></p>
Holger Hellinger<p>Wenn „Developer“ den Plain-Text-Teil einer E-Mail „vergessen“ und stattdessen den Rest für Dokumentation missbrauchen, sehen Menschen wie ich, die keine HTML-Mails lesen wollen, und Menschen, die darauf angewiesen sind, oft gar nichts mehr.</p><p>Ich merke das auch im Alltag: Vor 20 Jahren war es selbstverständlich, einen Plain-Text-Teil bereitzustellen. Heute denken viele nur noch: „Hat doch eh jeder HTML-Mails.“</p><p><a href="https://hellinger.wtf/tags/Barrieren" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Barrieren</span></a> <a href="https://hellinger.wtf/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a></p>
vruz<p>Web's superpower is its openness. Native JS templating makes JS more ergonomic. Direct WASM→DOM makes the web more OPEN. Which better serves the platform's future? The web shouldn't privilege one language. True platform evolution means equal access to core capabilities for all languages. That's how we get the next generation of web innovation. <a href="https://mstdn.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>compsci</span></a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webdev</span></a> <a href="https://mstdn.social/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webstandards</span></a> <a href="https://mstdn.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a></p>
vruz<p>The Web's superpower is its openness. Native JS templating makes JS more ergonomic. Direct WASM→DOM makes the web more OPEN. Which better serves the platform's future? The web shouldn't privilege one language. True platform evolution means equal access to core capabilities for all languages. That's how we get the next generation of web innovation. <a href="https://mstdn.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>compsci</span></a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webdev</span></a> <a href="https://mstdn.social/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webstandards</span></a> <a href="https://mstdn.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a></p>
Continued thread
Why add yet another JS templating API when WASM + direct DOM access solves the root problem? Every language could build efficient UIs without the JS bottleneck. More universal than blessing one syntax. Think beyond JavaScript - imagine Rust components with zero overhead, Go templates that actually perform, or C# Blazor without the bridge tax. That's true platform evolution. #compsci #webdev #wasm #webstandards
VegansExploreLive feeds
Mastodon is the best way to keep up with what's happening.
Follow anyone across the fediverse and see it all in chronological order. No algorithms, ads, or clickbait in sight.
Create accountLoginDrag & drop to upload