This repository has been archived by the owner on Apr 6, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 9
First item sometimes disappears with ComponentRenderer #232
Comments
pekam
added a commit
that referenced
this issue
Mar 13, 2019
because it breaks flow-component-renderer. Fix #232
pekam
added a commit
that referenced
this issue
Mar 18, 2019
because it breaks flow-component-renderer. Fix #232
pekam
added a commit
that referenced
this issue
Mar 18, 2019
because it breaks flow-component-renderer. Fix #232
pekam
added a commit
that referenced
this issue
Mar 18, 2019
because it breaks flow-component-renderer. Fix #232
pekam
added a commit
that referenced
this issue
Mar 19, 2019
because it breaks flow-component-renderer. Fix #232
pekam
added a commit
that referenced
this issue
Mar 21, 2019
because it breaks flow-component-renderer. Fix #232
pekam
added a commit
that referenced
this issue
Mar 21, 2019
because it breaks flow-component-renderer. Fix #232
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is caused by
iron-list
. It has an extra focus element, which duplicates the content of the first item.When you scroll down enough so that the
iron-list
reorders some of the item components, and then scroll back up, the component belonging to the first item may be rendered in the hidden focus element.Making sure that the
flow-component-renderer
in the first item attaches the component, after the focus element has "stolen" the rendered component instance, would fix the issue.An ugly workaround would be to disable the focus management by monkey-patching:
The focus management might not be needed by combo-box, since it should not contain focusable elements like inputs.
A related ticket for
iron-list
: PolymerElements/iron-list#511The text was updated successfully, but these errors were encountered: