[SF][ui5-toolbar]: consider element scoping in toolbar shared resources

[zhangliangyi]

Bug Description

I noticed that there is a shared resource registry in the new ui5-toolbar component. But right now, the pure tag name is used as the registry key.

ui5-webcomponents/packages/main/src/ToolbarRegistry.ts

Line 8 in 19475eb

registry.set(ElementClass.getMetadata().getPureTag(), ElementClass);

But considering the element scoping, if there are several ui5 contexts in the current runtime, the toolbar constructor would be polluted. All the toolbar components would use the first registered constructor even they have element scope defined for different versions.

Affected Component

ui5-toolbar

Expected Behaviour

Using tag name with element scoping as the registry key.

Isolated Example

No response

Steps to Reproduce

N/A

Log Output, Stack Trace or Screenshots

No response

Priority

Medium

UI5 Web Components Version

2.3.0

Browser

Edge

Operating System

No response

Additional Context

No response

Organization

SF

Declaration

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

[PetyaMarkovaBogdanova]

Hi team,
can you, please, review this enhancement request?
Best regards,
Petya Markova.
(UI5 Web Components Dispatcher)

[zhangliangyi]

This issue is a solid blocker when leveraging new toolbar component in our upgrade work. As a workaround, right now we have to roll back to the legacy toolbar in ui5-react.