chrome-extensions-samples
wpt
Our great sponsors
chrome-extensions-samples | wpt | |
---|---|---|
27 | 20 | |
14,254 | 4,627 | |
2.3% | 1.1% | |
8.5 | 10.0 | |
9 days ago | 3 days ago | |
JavaScript | HTML | |
Apache License 2.0 | 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.
chrome-extensions-samples
-
How do I make this extension?
You should be using the context menu API. You can check out some of the examples to have a better idea. This single file should get you all the info you need - context menu basic example.
-
How to objectively value code refactoring?
Hell, I even included the fix for the broken Google Chrome chrome-extensions samples Python Native Messaging host in a PR I filed to update their sample https://github.com/GoogleChrome/chrome-extensions-samples/pull/617/commits/c26521ed60d6028dd73c84a2b726a1889b6616f7.
-
How can I do this in manifest v3 too in my chrome extention.
There are some examples here https://github.com/GoogleChrome/chrome-extensions-samples/issues/662 and here https://github.com/GoogleChrome/chrome-extensions-samples/issues/784.
-
When do you think X.org will become "officially" deprecated?
What happens when you try to run this Native Messaging host application https://github.com/GoogleChrome/chrome-extensions-samples/blob/main/_archive/mv2/api/nativeMessaging/host/native-messaging-example-host on your current machine without modifying anything in the file or installing a package that links python to Python 2 and not Python 3?
-
10 Coding Projects to Impress Employers and Land Your Dream Job 😎
Chrome Extension Examples - a collection of sample Chrome extensions to learn from
- [AskJS] What are the worst case scenarios for programmatically setting arbitrary Web pages (Origins) as Client or WindowClient of a ServiceWorker?
-
Rookie question: How do I know I am making progress with my JS learning?
Another more involved challenge: Transfer (e.g., using Transferable objects) an ArrayBuffer from a ServiceWorker to an arbitrary Web page not controlled by or in the scope of the ServiceWorker - without using an element https://github.com/GoogleChrome/chrome-extensions-samples/issues/766.
-
How do I use this python parameter in javascript?
You can use Native Messaging to connect to and communicate with a native host, e.g., Python, from JavaScript client in the browser, see https://github.com/GoogleChrome/chrome-extensions-samples/pull/617/commits/a06b4e37b7a095f845a321b0cd7adac5a3b41f02.
-
Is there any way to programmatically set an MV3 ServiceWorker's WindowClient?
Take the time to carefully read this Google Chrome extension samples issue Sample: Transfer a blob from a background context to a page #766.
-
Content Security Policy Error for Chrome Extension
You can use declarativeNetRequest to remove content-security-policy for specific Web sites or all Web sites, see https://github.com/guest271314/remove-csp-header; https://github.com/GoogleChrome/chrome-extensions-samples/issues/662.
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.
What are some alternatives?
octotree - GitHub on steroids
browsh - A fully-modern text-based browser, rendering to TTY and browsers
react-native-universal-monorepo - React Native boilerplate supporting multiple platforms: Android, iOS, macOS, Windows, web, browser extensions, Electron.
firefox-ios - Firefox for iOS
vanced-website-v2 - Source Code of the Vanced Website
linkedom - A triple-linked lists based DOM implementation.
tampermonkey - Tampermonkey is the most popular userscript manager, with over 10 million users. It's available for Chrome, Microsoft Edge, Safari, Opera Next, and Firefox.
firefox-user.js-tool - Interactive view, compare, and more for Firefox user.js (eg arkenfox/user.js) + about:config functions
browser_extension - A browser extension that redirects popular sites to alternative privacy friendly frontends
caniuse - Raw browser/feature support data from caniuse.com
SingleFile-MV3 - SingleFile version compatible with Manifest V3. The future, right now!
ioccc - My IOCCC submissions and practice.