Displaying 1 to 20 from 92 results

jsdom - A JavaScript implementation of the WHATWG DOM and HTML standards, for use with node.js

  •    Javascript

jsdom is a pure-JavaScript implementation of many web standards, notably the WHATWG DOM and HTML Standards, for use with Node.js. In general, the goal of the project is to emulate enough of a subset of a web browser to be useful for testing and scraping real-world web applications.As of v10, jsdom has a new API (documented below). The old API is still supported for now; see its documentation for details.

document-register-element - A stand-alone working lightweight version of the W3C Custom Elements specification

  •    Javascript

A stand-alone lightweight version of Custom Elements V1 based on top, and compatible with, the battle-tested Custom Elements V0, already used in production with projects such Google AMP HTML ⚡ and others. If you specify noBuiltIn property as true, the V1 API will be polyfilled where needed, but no extra checks and patches will be applied to make custom elements built-in working, since no browser is currently shipping this part of the specification.

jsdom - A JavaScript implementation of the WHATWG DOM and HTML standards, for use with node.js

  •    Javascript

jsdom is a pure-JavaScript implementation of many web standards, notably the WHATWG DOM and HTML Standards, for use with Node.js. In general, the goal of the project is to emulate enough of a subset of a web browser to be useful for testing and scraping real-world web applications. As of v10, jsdom has a new API (documented below). The old API is still supported for now; see its documentation for details.




postcss-cssnext - :cyclone: PostCSS plugin to use tomorrow's CSS syntax, today.

  •    Javascript

PostCSS plugin to use tomorrow’s CSS syntax, today. PostCSS-cssnext is a PostCSS plugin that helps you to use the latest CSS syntax today. It transforms CSS specs into more compatible CSS so you don’t need to wait for browser support.

wpt - Test suites for Web platform specs — including WHATWG, W3C, and others

  •    HTML

The web-platform-tests Project is a W3C-coordinated attempt to build a cross-browser testsuite for the Web-platform stack. Writing tests in a way that allows them to be run in all browsers gives browser projects confidence that they are shipping software that is compatible with other implementations, and that later implementations will be compatible with their implementations. This in turn gives Web authors/developers confidence that they can actually rely on the Web platform to deliver on the promise of working across browsers and devices without needing extra layers of abstraction to paper over the gaps left by specification editors and implementors. Clone or otherwise get https://github.com/web-platform-tests/wpt.

postcss-preset-env - Convert modern CSS into something browsers understand

  •    CSS

PostCSS Preset Env lets you convert modern CSS into something most browsers can understand, determining the polyfills you need based on your targeted browsers or runtime environments. Without any configuration options, PostCSS Preset Env enables Stage 2 features and supports all browsers.

xmldom - A PURE JS W3C Standard based(XML DOM Level2 CORE) DOMParser and XMLSerializer.

  •    Javascript

A JavaScript implementation of W3C DOM for Node.js, Rhino and the browser. Fully compatible with W3C DOM level2; and some compatible with level3. Supports DOMParser and XMLSerializer interface such as in browser.


tributary - rapid prototyping with d3.js

  •    Javascript

Tributary allows you to share live-editable code snippets. These snippets will most likely use d3.js and allow a user to play with code in a very responsive way. Tributary is innovation on principle, taking the excellent work of Gabriel Florit which was in turn inspired by Bret Victor's genius and making it sharable.

csstree - A tool set for working with CSS including fast detailed parser, walker, generator and lexer based on W3C specs and browser implementations

  •    Javascript

CSSTree is a tool set to work with CSS, including fast detailed parser (string->AST), walker (AST traversal), generator (AST->string) and lexer (validation and matching) based on knowledge of spec and browser implementations. The main goal is to be efficient and W3C spec compliant, with focus on CSS analyzing and source-to-source transforming tasks. NOTE: The project is in alpha stage since some parts need further improvements, AST format and API are subjects to change. However it's stable enough and used by packages like CSSO (CSS minifier) and SVGO (SVG optimizer) in production.

respec - A tool for creating technical documents and web standards

  •    Javascript

ReSpec is a JS library that makes it easier to write technical specifications, or documents that tend to be technical in nature in general. It was originally designed for the purpose of writing W3C specifications, but has since grown to be able to support other outputs as well. If you are just interested in writing a spec, you can grab the starter spec.

node-Tor - Javascript implementation of the Tor (or Tor like) anonymizer project (The Onion Router)

  •    Javascript

For a quick look, see the demo video on Peersm, download and stream anonymously inside your browser, serverless anonynous P2P network compatible with torrents. Check out torrent-live for a more general presentation and to get the dynamic blocklist.

HandJS

  •    Javascript

Hand.js: a polyfill for supporting pointer events on every browser

webdriver-rust - Library implementing the wire protocol for the W3C WebDriver standard.

  •    Rust

As of right now this is an implementation for the server side of the WebDriver API in Rust, not the client side.

platform-status - Project Platform Status

  •    Javascript

Platform Status gives developers a cross-platform and cross-browser roadmap for browser features, from standardization and development to release. Not only a channel to raise awareness, it can also drive adoption and improve the vital feedback loop Firefox's platform needs to have with web developers. For most developers it will be a reference to discover and learn, but it has the potential to provide the entry points for radical participation on Mozilla's platform development.Existing web compatibility references, like caniuse focus on cross-browser compatibility but don't cover un-released features and lag behind on features that already shipped. Major browser vendors (Edge, Chrome, Webkit) are publicising their own platform status with references to their bug tracking and bug owners. Similar to Platform Status' goal, Chrome tracks consensus/enthusiasm from other browsers using sources that range from bugs, to IRC logs to tweets.

interledger-payment-app-example - An implementation of the Interledger spec through an Android's Payment App

  •    Java

This is a project that was done as part of a hack-o-thon organized at the Interledger Workshop at Blockchain Expo. This repo is meant as a showcase of an Android payment app, using the Interledger spec for payment.As such, it contains both the website implementation of the Payment Request and a Payment App itself. It does not contain the ledger implementations. These are hardcoded to use https://red.ilpdemo.org and https://blue.ilpdemo.org as originating and the destination ledgers. Both are running the NodeJS ILP kit and have been implemented as an initiative to show off the Interledger spec.

html-element-attributes - Map of HTML elements to allowed attributes

  •    Javascript

Map of HTML elements to allowed attributes. Also contains global attributes under '*'. Includes attributes from HTML 4, W3C HTML 5, and WHATWG HTML 5.Note: Includes deprecated attributes.

html-tag-names - List of known HTML tag-names

  •    Javascript

List of known HTML tag-names. Includes ancient (for example, nextid and basefont) and modern (for example, shadow and template) tag-names from both W3C and WHATWG.The repo includes a script to crawl W3C and WHATWG to include newly introduced tag-names.

html-void-elements - List of known void HTML elements

  •    Javascript

List of known void HTML elements. Includes ancient (for example, nextid and basefont) and modern (for example, img and meta) tag-names from both W3C and WHATWG.Note: there’s one special case: menuitem. W3C specifies it to be void, but WHATWG doesn’t. I suggest using the void form.





We have large collection of open source products. Follow the tags from Tag Cloud >>


Open source products are scattered around the web. Please provide information about the open source projects you own / you use. Add Projects.