[MGNLUI-127] CompositeComponent should not be faceless on client-side Created: 01/Nov/12  Updated: 15/Mar/13  Resolved: 15/Mar/13

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.0
Fix Version/s: 5.0

Type: Improvement Priority: Minor
Reporter: Mikaël Geljić Assignee: Mikaël Geljić
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)

 Description   

CompositeComponent is meant to be used in place of Vaadin's CustomComponent - it has the same server-side purpose and roughly same api, but saves one div.

Problem with current impl is that this composite is not painted at all to target (in the vaadin sense). Therefore server and client have different widget trees, and we are not sure how stable this is.



 Comments   
Comment by Mikaël Geljić [ 15/Mar/13 ]

used to be vaadin 6 issue with lightweight custom components

Generated at Mon Feb 12 08:33:51 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.