Browser
WHATWG HTML Standard
Our great sponsors
Browser | WHATWG HTML Standard | |
---|---|---|
5 | 137 | |
2,415 | 7,695 | |
- | 2.0% | |
0.0 | 9.4 | |
about 2 months ago | 4 days ago | |
Ruby | HTML | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Browser
-
Responsiveness, ERB and Tailwind - looking for best practices
Very interesting, thank you! I didn't know this variant feature on erb files. It would only work after a request is made (and not if a window is resized for example) but it seems powerful. I'll try it for sure. I have used this browser gem in the past which helped me achieve something similar for specific cases, but this seems cleaner.
-
My project: railstart app
browser
-
railstart-niceadmin support more features
- [browser](https://rubygems.org/gems/browser)
-
A gem to know the users devices
I’ve always used the browser gem to detect devices. It wirks really well, and it is still being maintained
-
Has anyone here benchmarked device_detector VS browser gems
I have not benchmarked them but if you're porting old code to Browser beware that sometimes its predicate methods return true, sometimes false, and, sometimes: nil.
WHATWG HTML Standard
-
Here are the 10 projects I am contributing to over the next 6 months. Share yours
WHAT-WG HTML
- Add Writingsuggestions="" Attribute
-
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
-
YouTube video embedding harm reduction
The `allow` attribute on iframes is a relatively recent API addition from 2017
https://github.com/whatwg/html/pull/3287
-
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.
- HTML Living Standard
-
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
What are some alternatives?
Device Detector - DeviceDetector is a precise and fast user agent parser and device detector written in Ruby
caniuse - Raw browser/feature support data from caniuse.com
UserAgent - HTTP User Agent parser
WebKit - Home of the WebKit project, the browser engine used by Safari, Mail, App Store and many other applications on macOS, iOS and Linux.
desktop - The desktop vault (Windows, macOS, & Linux).
standards-positions
hoppscotch-extension - 🧩 Browser extensions to provide more capabilities to https://hoppscotch.io
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.
ffsend - :mailbox_with_mail: Easily and securely share files from the command line. A fully featured Firefox Send client.
browser
passman - 🔐 Open source password manager with Nextcloud integration
exploits