wpt
sciter
wpt | sciter | |
---|---|---|
20 | 85 | |
4,663 | 2,560 | |
0.8% | -0.1% | |
10.0 | 0.0 | |
4 days ago | about 1 year ago | |
HTML | C++ | |
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.
wpt
-
Show HN: Dropflow, a CSS layout engine for node or <canvas>
To reply mostly with my WPT Core Team hat off, mostly summarising the history of how we've ended up here:
A build script used by significant swaths of the test suite is almost certainly out; it turns out people like being able to edit the tests they're actually running. (We _do_ have some build scripts — but they're mostly just mechanically generating lots of similar tests.
A lot of the goal of WPT (and the HTML Test Suite, which it effectively grew out of) has been to have a test suite that browsers are actually running in CI: historically, most standards test suites haven't been particularly amenable to automation (often a lot of, or exclusively, manual tests, little concern for flakiness, etc.), and with a lot of policy choices that effectively made browser vendors choose to write tests for themselves and not add new tests to the shared test suite: if you make it notably harder to write tests for the shared test suite, most engineers at a given vendor are simply going to not bother.
As such, there's a lot of hesitancy towards anything that regresses the developer experience for browser engineers (and realistically, browser engineers, by virtue of sheer number, are the ones who are writing the most tests for web technologies).
That said, there are probably ways we could make things better: a decent number of tests for things like Grid use check-layout-th.js (e.g., https://github.com/web-platform-tests/wpt/blob/f763dd7d7b7ed...).
One could definitely imagine a world in which these are a test type of their own, and the test logic (in check-layout-th.js) can be rewritten in a custom test harness to do the same comparisons in an implementation without any JS support.
The other challenge for things like Taffy only targeting flexbox and grid is we're unlikely to add any easy way to distinguish tests which are testing interactions with other layout features (`position: absolute` comes to mind!).
My suggestion would probably be to start with an issue at https://github.com/web-platform-tests/rfcs/issues, describing the rough constraints, and potentially with one or two possible solutions.
-
The Ladybird Browser Project
It also helps that there are tests
https://web-platform-tests.org/
-
Making Web Component properties behave closer to the platform
You can see how Mozilla tests the compliance of their built-in elements in the Gecko repository (the ok and is assertions are defined in their SimpleTest testing framework). And here's the Web Platform Tests' reflection harness, with data for each built-in element in sibling files, that almost every browser pass.
-
We're building a browser when it's supposed to be impossible
We have our own test suite (orginally derived from the test suite of Meta's Yoga layout library [0]) which consists of text fixtures that are small HTML snippets [1] and a test harness [2] that turns those into runnable tests, utilising headless chrome both to parse the HTML and to generate the assertions based on the layout that Chrome renders (so we are effectively comparing our implementation against Chrome). We currently have 686 generated tests (covering both Flexbox and CSS Grid).
We would like to utilise the Web Platform Test suite [3], however these are not in a standard format and many of the tests require JavaScript so we are not currently able to do that.
[0]: https://github.com/facebook/yoga
[1]: https://github.com/DioxusLabs/taffy/tree/main/test_fixtures
[2]: https://github.com/DioxusLabs/taffy/tree/main/scripts/gentes...
[3]: https://github.com/web-platform-tests/wpt/tree/master/css/cs...
-
What new CSS and JavaScript features can we expect soon? Or is it all unexpected?
The metrics are based on the passing rate for the web-platform-tests (WPT) project, the automated test suite for web standards. The completion rate is categorised as either stable, or experimental. There is no definition of what experimental entails, presumably features that are behind experimental flags are included. Stable is better to go off in any case.
-
[AskJS] MSE quality resources
Depends on what you are trying to achieve. You can run WPT MSE https://github.com/web-platform-tests/wpt/tree/master/media-source and WebCodecs https://github.com/web-platform-tests/wpt/tree/master/webcodecs tests manually to learn by doing.
-
Rookie question: How do I know I am making progress with my JS learning?
Manually running the tests in Web Platform Tests should keep you busy.
-
Browsers Running Old JS Engines
Not sure what you mean? I referred to Web API's, which generally means Web platform API's; that is Web platform API's tested by Web Platform Tests https://github.com/web-platform-tests/wpt.
-
State of CSS
If you want CSS to be the same across browsers then help implement CSS tests and file bugs
https://www.w3.org/Style/CSS/Test/Overview.en.html
https://web-platform-tests.org/
better specs are great, but tests will actually find the edge cases and lead to more convergence.
-
How do I go about learning advanced DOM manipulation with vanilla JS?
Run all these tests locally https://github.com/web-platform-tests/wpt/tree/master/dom.
sciter
- Show HN: Open Source TailwindCSS UI Components
-
Show HN: Dropflow, a CSS layout engine for node or <canvas>
> wondering if css and svg could be used as abstraction over graphics and UI libraries
There's another project called Sciter that uses CSS to target native graphics libraries: https://sciter.com
> I wonder how hard it was to implement css. I've heard it can be pretty complex.
It was hard, but the biggest barrier is the obscurity of the knowledge.
Text layout is the hardest, because working with glyphs and iterating them in reverse for RTL is brain-breaking. And line wrapping gets really complicated. It's also the most obscure because nobody has written down everything you need to know in one place. After I finished block layout early on, I had to stop for a couple of years (only working a few hours a week though) and learn all of the ins, outs, dos, and don'ts around shaping and itemizing text. A lot of that I learned by reading Pango's [1] source code, and a lot I pieced together from Google searches.
But other than that, the W3C specifications cover almost everything. The CSS2 standard [2] is one of the most beautiful things I've ever read. It's internally consistent, concise, and obviously the result of years of deliberation, trial and error. (CSS3 is great, but CSS2 is the bedrock for everything).
[1] https://gitlab.gnome.org/GNOME/pango/
- Ask HN: Fastest cross-platform GUI stack/strategy
- Bringing Back Horizontal Rules in HTML Select Elements
-
Immediate Mode GUI Programming
otherwise, if we have only retained mode as in browsers, we will need to modify the DOM heavily and create temporary elements for handles.
[1] https://sciter.com
- This year in Servo: over 1000 pull requests and beyond
-
Rusty revenant Servo returns to render once more
I've still never used it but I've long been curious about Sciter:
https://sciter.com
- Ode to the M1
-
So you want to write a GUI framework (2021)
These bullet points are exactly what I did in Sciter (https://sciter.com)
- Windowing
-- Tabs
-- Menus
-- Painting
-- Animation
-- Text
-The compositor
-Handling input
-- Pointer input
-- Keyboard input
- Accessibility
- Internationalization and localization
- Cross-platform APIs
- The web view
- Native look and feel
On top of that DOM and CSS implementations to achieve declarative UI. And JS as a languuage behind UI - declarative in some sense way of defining UI behavior.
-
Servo, the parallel browser engine written in Rust
I'm not sure if it can support all the libraries but yes it can be used to make desktop apps. Theres also Sciter.
https://sciter.com/
What are some alternatives?
browsh - A fully-modern text-based browser, rendering to TTY and browsers
webview - Tiny cross-platform webview library for C/C++. Uses WebKit (GTK/Cocoa) and Edge WebView2 (Windows).
firefox-ios - Firefox for iOS
qt - Qt binding for Go (Golang) with support for Windows / macOS / Linux / FreeBSD / Android / iOS / Sailfish OS / Raspberry Pi / AsteroidOS / Ubuntu Touch / JavaScript / WebAssembly
linkedom - A triple-linked lists based DOM implementation.
tauri - Build smaller, faster, and more secure desktop applications with a web frontend.
caniuse - Raw browser/feature support data from caniuse.com
flexboard - React component library for re-sizable sidebars
firefox-user.js-tool - Interactive view, compare, and more for Firefox user.js (eg arkenfox/user.js) + about:config functions
RmlUi - RmlUi - The HTML/CSS User Interface library evolved
ioccc - My IOCCC submissions and practice.
NanoGUI - Minimalistic GUI library for OpenGL