SaaSHub helps you find the best software and product alternatives Learn more →
WHATWG HTML Standard Alternatives
Similar projects and alternatives to WHATWG HTML Standard
-
-
WebKit
Home of the WebKit project, the browser engine used by Safari, Mail, App Store and many other applications on macOS, iOS and Linux.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
Retroactive
Retroactive only receives limited support. Run Aperture, iPhoto, and iTunes on macOS Sonoma, macOS Ventura, macOS Monterey, macOS Big Sur, and macOS Catalina. Xcode 11.7 on macOS Mojave. Final Cut Pro 7, Logic Pro 9, and iWork ’09 on macOS Mojave or macOS High Sierra.
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
TypeScript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
breaking-changes-web
💢 A list of breaking changes to the web platform
-
-
-
-
-
-
-
rupy
HTTP App. Server and JSON DB - Shared Parallel (Atomic) & Distributed
-
-
Servo
Servo, the embeddable, independent, memory-safe, modular, parallel web rendering engine
-
keepassxc
KeePassXC is a cross-platform community-driven port of the Windows application “Keepass Password Safe”.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
WHATWG HTML Standard reviews and mentions
-
Streaming HTML out of order without JavaScript
There's a long-standing WHATWG feature request open for it here: https://github.com/whatwg/html/issues/2791
And several userland custom element implementation, like https://www.npmjs.com/package//html-include-element
One of the cool things that you can do with client-side includes and shadow DOM is render the included HTML into a shadow root that has s, so that the child content of the include element is slotted into a shell implemented by the included HTML.
This lets you do things like have the main page be the pre-page content and the included HTML be a heavily cached site-wide shell, and then another per-user include with personalized HTML - all cached appropriately.
-
An HTML Switch Control
As mentioned by others, OK idea, but not a fan that this isn't standardized. After a quick search+peruse, these seem to indicate that it's not around the corner either. Happy (/hope) to be corrected.
-
YouTube video embedding harm reduction
The `allow` attribute on iframes is a relatively recent API addition from 2017
-
Htmz – a low power tool for HTML
I think there's a pretty strong argument at this point for this kind of replacing DOM with a response behavior being part of the platform.
I think the first step would be an element that lets you load external content into the page declaratively. There's a spec issue open for this: https://github.com/whatwg/html/issues/2791
And my custom element implementation of the idea: https://www.npmjs.com/package/html-include-element
Then HTML could support these elements being targets of links.
-
The Ladybird Browser Project
> Consider https://www.ietf.org/rfc/rfc1866.txt vs https://html.spec.whatwg.org/multipage/
I thought, oh, that's not so bad. Then I realized what I was looking at was a 10 page index.
> if we're finally seeing fruits of browsers being better standardized on "95%"+ of the popular features -- and if writing a browser today is in fact easier than both writing AND maintaining a browser a decade back.
A decade back, maybe... but decades ago the number of things you had to support was just so much smaller even if you only look at HTML! Consider https://www.ietf.org/rfc/rfc1866.txt vs https://html.spec.whatwg.org/multipage/
-
Is Htmx Just Another JavaScript Framework?
I'd love to see something like HTMX get standardized, but I'm extremely pessimistic for HTMX's prospects for standardization in HTML.
In talking to a few standards folks about it, they've all said, "oh, yeah, you want declarative AJAX; people have tried and failed to get that standardized for years." Even just trying to get
to target a section of the page that isn't an has been argued about and hashed out for years.<p>Why is that? Well, for example, here's the form you have to fill out to start standardizing a front-end feature. <a href="https://github.com/whatwg/html/issues/new?assignees=&labels=addition%2Fproposal%2Cneeds+implementer+interest&projects=&template=1-new-feature.yml">https://github.com/whatwg/html/issues/new?assignees=&labels=...</a><p>It asks three main questions:<p>* What problem are you trying to solve? -
New in Chrome 120 back button detection
The issue with a single global event handler is discussed here: https://github.com/WICG/close-watcher#a-single-event
If you use popover="", you get the kind of functionality you're discussing for free. For
, the discussion is in progress and reaching a conclusion: https://github.com/whatwg/html/issues/9373 -
HTML Web Components: An Example
Do you mean like Declarative Shadom Dom?
-
A note from our sponsor - SaaSHub
www.saashub.com | 29 Mar 2024
Stats
whatwg/html is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of WHATWG HTML Standard is HTML.
Popular Comparisons
- WHATWG HTML Standard VS caniuse
- WHATWG HTML Standard VS WebKit
- WHATWG HTML Standard VS Retroactive
- WHATWG HTML Standard VS standards-positions
- WHATWG HTML Standard VS browser
- WHATWG HTML Standard VS breaking-changes-web
- WHATWG HTML Standard VS exploits
- WHATWG HTML Standard VS serenity
- WHATWG HTML Standard VS TypeScript
- WHATWG HTML Standard VS EventSource