Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Administered by:

Server stats:

225
active users

eupolicy.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.8

#webstandards

2 posts2 participants0 posts today
Public *
Timo Tijhof

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.

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*!

This is most noticable on modern high-DPI screens. It is rather unsatisfying, and hard to unsee...

Example:
en.wikipedia.org/wiki/Template

#css#WebDesign#WebStandards
Public *
Holger Hellinger

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.

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.“

Bestellung ***** bestätigt Bikers Base - 96 /* What it does: Remove spaces around the email design added by some email clients. */ /* Beware: It can remove the padding / Margin and add a background color to the
#Barrieren#WebStandards
Continued thread
Public
vruz

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. #compsci #webdev #webstandards #opensource

Public
vruz

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. #compsci #webdev #webstandards #opensource

Continued thread
Public
vruz

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

Public
xoron :verified:

File encryption with a browser.

I've been exploring the #WebCryptoAPI and I'm impressed!

When combined with the #FileSystemAPI, it offers a seemingly secure way to #encrypt and #store files directly on your device. Think #localstorage, but with #encryption!

I know #webapps can have #security vulnerabilities since the code is served over the web, so I've #OpenSourced my demo! You can check it out, and it should even work if #selfhosted on #GitHubPages.

Live Demo: dim.positive-intentions.com/?p

Demo Code: github.com/positive-intentions

Hook Code: github.com/positive-intentions

IMPORTANT NOTES (PLEASE READ!):
* This is NOT a product. It's for #testing and #demonstration purposes only.
* It has NOT been reviewed or audited. Do NOT use for sensitive data.
* The "password encryption" currently uses a hardcoded password. This is for demonstration, not security.
* This is NOT meant to replace robust solutions like #VeraCrypt. It's just a #proofofconcept to show what's possible with #browser #APIs.

dim.positive-intentions.com@storybook/core - Storybook
#Cryptography#JavaScript#Frontend
Public
Timo Tijhof

You'd think Google, having launched schema.org, knows how to produce valid schema.org metadata and HTML5.

YouTube: How about a `<span>` inside the head, and `<link rel=alternative>` inside the body?

HTML5 parsers:
Thanks, I'll take that span as your implied end of `<head>`, and raise you an implied start of `<body>`. Everything that follows is now part of the body.

Context:
github.com/Ranchero-Software/N

GitHubFeature request: construct feed URLs for YouTube channels · Issue #902 · Ranchero-Software/NetNewsWireBy superlex
#NetNewsWire#WebStandards#whatwg
Public
W3C Developers

Congrats to editors Matt Garrish and @tzviya for the two newly published @w3c #WebStandards "Digital Publishing WAI-ARIA Module 1.1 (DPUB-ARIA)" and "Digital Publishing Accessibility API Mappings 1.1 (DPUB-AAM)". #timetoadopt

▶️ w3.org/TR/dpub-aria-1.1/
▶️ w3.org/TR/dpub-aam-1.1/

www.w3.orgDigital Publishing WAI-ARIA Module 1.1Enabling users of assistive technologies to find their way through web content requires embedding semantic metadata about web document structural divisions. This is particularly important for structural divisions of long-form documents and goes along with embedding semantic metadata about web-application widgets and behaviors for assistive technologies. This specification defines a set of WAI-ARIA roles that are specific to helping users of assistive technologies navigate through such long-form documents.
#ebooks#accessibility
Public *
Steve Faulkner

🗿 the ARIA combobox role has gone through some changes during its specified life. It is worth reading about it in its latest incarnation in ARIA 1.3

#aria #a11y #WebStandards

w3c.github.io/aria/#combobox

w3c.github.ioAccessible Rich Internet Applications (WAI-ARIA) 1.3Accessibility of web content requires semantic information about widgets, structures, and behaviors, in order to allow assistive technologies to convey appropriate information to persons with disabilities. This specification provides an ontology of roles, states, and properties that define accessible user interface elements and can be used to improve the accessibility and interoperability of web content and applications. These semantics are designed to allow an author to properly convey user interface behaviors and structural information to assistive technologies in document-level markup. This version adds features new since WAI-ARIA 1.1 [wai-aria-1.1] to improve interoperability with assistive technologies to form a more consistent accessibility model for [HTML] and [SVG2]. This specification complements both [HTML] and [SVG2].
Public
Web Accessibility Initiative

W3C Accessibility Specialist Daniel Montalvo will be at the Inclusive Africa Conference 3–5 June 2025.

Daniel’s sessions are available free for remote participants:
- 12.10pm (EAT), 3 June: Global Implementation of Accessibility
- 2.40pm (EAT), 3 June: Roundtable on Developing Africa’s Digital Accessibility Standard

Registration: kutanaevents.com/events/inclus

#DigitalAccessibility
#WAI
#WebStandards

kutanaevents.comInclusive Africa Conference 2025 | Kutana EventsHost Inclusive events
Public
It's Richie

As we consider ways to implement #ActivityPub into our FOSS Community Calendar Ecosystem platform Koalagator, I've been looking over the differing specs for how to specify the event object schema.

Have any other folk wrestled with this?Asking before I get arms deep in this stuff.

For those playing at home...

---
Schema.org - Event

Schema.org is a collaborative, community activity with a mission to create, maintain, and promote schemas for structured data on the Internet.

schema.org/Event

-----
W3C Activity Vocabulary - Event

This specification describes the Activity vocabulary. It is intended to be used in the context of the ActivityStreams 2.0 format and provides a foundational vocabulary for activity structures, and specific activity types.

w3.org/TR/activitystreams-voca

----

Fediverse Enhancement Proposal
FEP-8a8e: A common approach to using the Event object type

ActivityStreams defines the Object Type Event. In real-world applications, the event object immediately showed the need for extension. Applications featuring Event objects have often chosen to add additional attributes and clarifications (i.e., interpretations) in order to implement their particular use case. This proposal clarifies and extends the ActivityPub standard to address the needs that have arisen in real-world implementations.

codeberg.org/linos/fep/src/bra

---

[HTML] Microformats - h-event

People are using microformats to mark up profiles, posts, events and other data on their personal sites, enabling developers to build applications which use this data in useful and interesting ways.

microformats.org/wiki/h-event

---

iCalendar Standard (RFC 5545)

iCalendar was first defined as a standard as RFC 2445 in 1998 by the Internet Engineering Task Force (IETF). Today, iCalendar is used to import and synchronize events on various platforms, including smart phones, computer and web applications.

icalendar.org/the-icalendar-st

schema.orgEvent - Schema.org TypeSchema.org Type: Event - An event happening at a certain time and location, such as a concert, lecture, or festival. Ticketing information may be added via the <a class="localLink" href="/offers">offers</a> property. Repeated events may be structured as separate Event objects.
#Calendar#Standards#WebStandards
Public
Steve Faulkner

Quick guidance for referring to (parts of) HTML elements By @yatil

“You always need to be very clear in what you mean. Otherwise, it is hard to read for your audience…”

#HTML #webStandards

micro.yatil.net/2023/07/23/qui

micro.yatil.net · Quick guidance for referring to (parts of) HTML elementsYou always need to be very clear in what you mean. Otherwise, it is hard to read for your audience. Always include brackets with the element names. You can differentiate attributes and values by using these words. Always include the word “value” when talking about values. First mention of an element: “<h1> element” First mention of an attribute: “id attribute” First mention of a value: “my-great-id value” Subsequent mention of an element: “<h1>” or “<h1> element” Subsequent mention of an attribute: “id” or “id attribute” Subsequent mention of a value: “my-great-id value” Avoid the use of “tag” when the whole element is the subject of the sentence, do only use “tag” when it is specific to the start or end tag.
ExploreLive feeds
About