List view
Custom elements should be reliable, by: - being supported in all browsers - having full spec-compliant implementations - i.e. including extending builtin elements. - being compatible with all frameworks/libraries - see https://custom-elements-everywhere.com/ - no flash of unstyled content - etc.
No due date•3/3 issues closedImplementing mandatory elements is not enough for applications. Complex application deal with adding, updating and listing of data, so we need to provide common UIs for those purposes.
No due date•21/21 issues closedDocumentation should be interactive and composed of doclets within the source code.
No due date•10/10 issues closedOur polyfills can be optimised and initial rendering is super slow.
No due date•9/9 issues closedFor several reasons it would be ideal to render any web-component isomorphically directly on the server, to: - remove FOUC - improve SEO - improve Speed
No due dateWe needs awesome tests - Linting - Unit Test for js utilities - Integration Tests for components (and their integration within React, Angular, you name it) - Cross Browser tests on BrowserStack - Failing Tests need to block PRs
No due date•5/5 issues closedSevreal utilities can be seperated: - Lifecycle - Context - Properties - State
No due date•3/3 issues closedWe need to provide several builds, like: - ES Modules (`.mjs` files) installed through NPM to enable custom builds for consumers - UMD/IFEE static files for legacy consumers including a common chunk file
No due date•44/44 issues closedThe PR for React Integration by `withReact` needs thorough testing to be done.
No due date•23/23 issues closed