ui5-table: component breaks if imported from both the main and compat package

[Lukas742]

Bug Description

If both the Table from the compat package and the main package are used in the same app, the component breaks because the custom element tag name is the same for both tables.

I'm not sure if this can be supported without a breaking change, but if not, it should probably be mentioned in the documentation.

Related UI5WCR issue: SAP/ui5-webcomponents-react#6344

Affected Component

ui5-table

Expected Behaviour

No response

Isolated Example

https://stackblitz.com/edit/github-9tzm9t?file=main.js,index.html

Steps to Reproduce

1. Open the StackBlitz example
2. Observe that both tables are broken.
3. Comment out the imports for one of the tables.
4. See that the other table is now displaying as intended.

Log Output, Stack Trace or Screenshots

No response

Priority

None

UI5 Web Components Version

2.2.0

Browser

Chrome, Edge, Firefox, Safari

Operating System

No response

Additional Context

No response

Organization

No response

Declaration

• I’m not disclosing any internal or sensitive information.

[ilhan007]

Hi @Lukas742 both tables use the ui5-table tag and one should choose the one or the other. We will state it more prominently.

[pskelin]

The assumption for that was, that you won't use both tables from the same app, you will either use the compat table or upgrade to the new table.

For the micro front end scenarios, they will be in a different bundle and will have to use scoping anyway, so there won't be a clash.