web-padawan / lit-components

Moved to https://github.com/vaadin/component-mixins

🚨 Moved to vaadin/component-mixins 🚨

This repo was a research project and is now archived.

We are actively working on converting Vaadin components to LitElement and TypeScript.

Read more at https://vaadin.com/blog/next-generation-vaadin-components

lit-components's Issues

[research] Implement simplified FlattenedNodesObserver

In scope of this project, only some parts of FlattenedNodesObserver are being used. We could consider dropping it at all, and listen to slotchange event, the only concern here is that we still should take care of tracking removed nodes, in order to be able to remove event listeners:

lit-components/packages/radio-group-base/lit-radio-group-base.js

Line 135 in efcd7b0

button.removeEventListener('checked-changed', checkedChangedListener);

TypeScript?

Have you considered doing this in TypeScript? As a first step renaming from js to ts and a bit of tsconfig should do.

[research] Flexbox scroller for combo-box and grid

Discussed many times as a possible replacement for iron-list
The idea is to use order property to manage DOM nodes

When I split the WebPack to two files - Error Failed to execute 'define' on 'CustomElementRegistry': the name "dom-module" has already been used with this registry

Hi,

When I split the WebPack to two files and tried import both the files in index.html. I am getting an error what could be the reason behind? I have the commons going to vendor.js.

dom-module.js:163 Uncaught DOMException: Failed to execute 'define' on 'CustomElementRegistry': the name "dom-module" has already been used with this registry at Module../node_modules/@polymer/polymer/lib/elements/dom-module.js (http://10.83.44.18:8080/dropdown.js:5270:16) at __webpack_require__ (http://10.83.44.18:8080/dropdown.js:20:30) at Module../node_modules/@polymer/polymer/lib/utils/style-gather.js (http://10.83.44.18:8080/dropdown.js:19191:81) at __webpack_require__ (http://10.83.44.18:8080/dropdown.js:20:30) at Module../node_modules/@polymer/polymer/lib/mixins/element-mixin.js (http://10.83.44.18:8080/dropdown.js:9050:80) at __webpack_require__ (http://10.83.44.18:8080/dropdown.js:20:30) at Module../node_modules/@polymer/polymer/polymer-element.js (http://10.83.44.18:8080/dropdown.js:20310:86) at __webpack_require__ (http://10.83.44.18:8080/dropdown.js:20:30) at Module../packages/drop-down/sh-icon.js (http://10.83.44.18:8080/dropdown.js:23990:93) at __webpack_require__ (http://10.83.44.18:8080/dropdown.js:20:30)

Regards
Basanth

[research] Implement ThemableMixin similar to Polymer version

Starting from lit/lit-element#470,finalize method is now protected and is used to collect styles from the prototype chain. We can try to use that point to collect additional style modules for shadow parts, roughly the same as ThemableMixin works. Also, the _getUniqueStyles method looks as what we could override (but that one is private and we should use it carefully).

[research] Implement combo-box using virtual-scroller

Current state of project

Hi there, I'm so excited to have found this repo! What is current state of this project? I have a significant amount of experience with lit-element, in addition to having worked with polymer since polymer 1. Are you looking for a helping hand? I'd be happy to contribute!

[research] Investigate component dependency injection patterns

At this point, the base classes in this repo do not register themselves, delegating that to the "themed" extensions. However, that won't work once we start building complex components like combo-box.

One option would be to use "UnsafeStatic" extension proposed at lit/lit#568

[research] Implement grid using virtual-scroller

Prototype by Tomi: https://github.com/vaadin/vaadin-grid/tree/proto-virtual-scroller

[research] Implement form component

See the rationale and initial thoughts at vaadin/vaadin-core#207

[details] Implement animated transitions

[accordion] Expand content to full available height

This was considered a core feature, however I feel like it can be excluded from MVP.

[refactor] Reimplement lighter Gestures version

The Polymer gestures system is quite heavy and some parts of it are considered legacy:

The tap event is included in the gesture event mixin for backwards compatibility, but it's no longer required in modern mobile browsers.

https://polymer-library.polymer-project.org/3.0/docs/devguide/gesture-events

We should check what parts are used by our components (e.g. track is used in few places) and whether they can be refactored to not use gestures at all. Also we need to handle contextmenu