primeflex
standards-positions
Our great sponsors
primeflex | standards-positions | |
---|---|---|
3 | 175 | |
549 | 592 | |
4.9% | 2.2% | |
8.3 | 7.6 | |
7 days ago | about 1 month ago | |
JavaScript | Python | |
MIT License | Mozilla Public License 2.0 |
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.
primeflex
-
WebKit Supports Nested CSS
People want freedom (as seen by the down-votes this comment seems to have gathered) and I do remember the old times when I was very excited for the creativity SASS gave me.
Then in-between then and now, I did a lot of consulting work, and now I'm strongly feeling that the more DRY you try to make CSS, the more you end up writing, and unmaintainable CSS at that. Random example:
https://github.com/primefaces/primeflex/blob/master/_sass/li...
SASS is too powerful for its own good.
TL;DR: I wholeheartedly agree with the above comment.
-
Do you use Vue for smaller static sites?
I guess you know about this https://github.com/primefaces/primeflex/issues/93
standards-positions
-
Tailwind CSS v4.0.0 Alpha
Hasn't FireFox been dragging their asses on @scope? https://github.com/mozilla/standards-positions/issues/472
It took years to just convince them of the need for it. And I'm not sure anyone got convinced vs Chrome had already shipped it and Safari has it planned so they caved in.
Hard to believe FireFox used to be a leader of the modern web.
-
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.
-
Platform issues which disadvantage Firefox compared to first-party browsers
Mozilla's position on these specs is nicely outlined publicly and transparently as part of their standards-positions project: https://github.com/mozilla/standards-positions/issues/100
I'm kinda glad it's not implemented in my browser, to be honest, because the whole thing seems like a security nightmare.
It's a shame it impacts some hobby usecases, but I don't think this outweighs the reasoning set out on the GitHub issue.
-
What Progressive Web App (PWA) Can Do Today
This should have big warnings on it. Some of these are not web standards; they are features implemented unilaterally by Google in Blink that have been explicitly rejected by both Mozilla and Apple on privacy and security grounds.
Take Web Bluetooth, for example:
Mozilla:
> This model is unsustainable and presents a significant risk to users and their devices.
— https://mozilla.github.io/standards-positions/#web-bluetooth
Apple:
> Here are some examples of features we have decided to not yet implement due to fingerprinting, security, and other concerns, and where we do not yet see a path to resolving those concerns
— https://webkit.org/tracking-prevention/
This is Microsoft’s Embrace, Extend, and Extinguish bullshit applied to the web platform by Google. Google keeps implementing these things despite all other major rendering engines rejecting them, convinces people that they are part of the web, resulting in sites like this, then people start asking why Firefox and Safari are “missing functionality”. These are not part of the web platform, they are Google APIs that have been explicitly rejected.
-
Why Are Tech Reporters Sleeping on the Biggest App Store Story?
Is BLE a PWA requirement? I think they explained their position pretty well here, regardless of whether I agree:
https://github.com/mozilla/standards-positions/issues/95#iss...
-
Reason to Use Firefox Is Sync That Works
I took a glance at Can I Use what the difference between the last public release of Firefox and Chrome is [1] and they don't really have that big of a difference in the eyes of normal use-cases? Some of these aren't implemented purely because of privacy reasons, the proposals aren't finished yet or complexity [2].
Why would Firefox need to change to Chromium engine? The only websites I notice that don't work with Firefox is because of user-agent targetting or just putting 5-second time-outs in Youtube code on non-chrome webbrowsers [3].
Can you give some examples of websites not working on Firefox?
[1] https://caniuse.com/?compare=chrome+120%2Cfirefox+121&compar...
[2] https://mozilla.github.io/standards-positions/
[3] https://www.neowin.net/news/youtube-seemingly-intentionally-...
-
CSS Is Fun Again
Mozilla are dragging their heels on @scope:
https://github.com/mozilla/standards-positions/issues/472
https://connect.mozilla.org/t5/ideas/implement-css-scope-rul...
Someone who clearly didn't get it was wasting three years time "well actually"ing everything. The latest news is "it's worth prototyping". Meanwhile Chrome has released it(steam rolled?) and Safari has it in tech preview.
I question if FireFox has the resources to keep up with the pace of the modern web.
-
QEMU-iOS, an emulator for legacy Apple devices
Web Bluetooth is not a standard and is not on track to ever become a standard, e.g. "This specification was published by the Web Bluetooth Community Group. It is not a W3C Standard nor is it on the W3C Standards Track."
It is also not supported on any version of Firefox, for the same reasons. Here's Mozilla's "considered harmful" GitHub issue. https://github.com/mozilla/standards-positions/issues/95
-
Firefox on the brink?
Also firefox development has slowed and they're starting to fall behind. They still don't have web serial for instance due to pure stupidity. https://github.com/mozilla/standards-positions/issues/336
What are some alternatives?
webcontainer-core - Dev environments. In your web app.
Tailwind CSS - A utility-first CSS framework for rapid UI development.
WHATWG HTML Standard - HTML Standard
wpt - Test suites for Web platform specs — including WHATWG, W3C, and others
WebKit - Home of the WebKit project, the browser engine used by Safari, Mail, App Store and many other applications on macOS, iOS and Linux.
firefox-ios - Firefox for iOS
vite - Next generation frontend tooling. It's fast!
Fakeflix - Not the usual clone that you can find on the web.
storage-foundation-api-explainer - Explainer showcasing a new web storage API, NativeIO
uBlock-Safari - uBlock Origin - An efficient blocker for Chromium, Firefox, and Safari. Fast and lean.
caniuse - Raw browser/feature support data from caniuse.com
brave-browser - Next generation Brave browser for Android, Linux, macOS, Windows.