SAP / openui5

OpenUI5 lets you build enterprise-ready web applications, responsive to all devices, running on almost any browser of your choice.
http://openui5.org
Apache License 2.0
2.95k stars 1.23k forks source link

duplicateId error on SemanticPage footerCustomActions with binding #3778

Closed pixel-fabian closed 1 year ago

pixel-fabian commented 1 year ago

OpenUI5 version: 1.108 also tested with 1.114.0, bug is still present.

Browser/version (+device/version): Chrome: 114.0.5735.110 (Official Build) (64-bit) on Windows10

Any other tested browsers/devices(OK/FAIL): Firefox: 113.0.2 on Windows10 (FAIL)

URL (minimal example if possible): https://github.com/pixel-fabian/ui5-playground/tree/main/01_binding-customfooteractions

Steps to reproduce the problem:

  1. Have a app with a SemanticPage where the footerCustomActions are bound to a model
  2. On loading the footerCustomActions the first time it works fine
  3. Navigate between different pages and reset the data on the binding at one point
  4. On loading the footerCustomActions the second time you get a duplicateID error

What is the expected result? The footerCustomActions should update according to binded data

What happens instead? duplicateID error

Any other information? (attach screenshot if possible) On loading the page the first time, the footerCustomActions are displayed properly and have the following IDs:

  1. __button0-container-ui5.playground.customfooteractions---Page1--page1-0
  2. __button0-container-ui5.playground.customfooteractions---Page1--page1-1

grafik

On loading the page the second time:

  1. __button0-container-ui5.playground.customfooteractions---Page1--page1-0 is gone from the DOM
  2. In __button0-container-ui5.playground.customfooteractions---Page1--page1-1 the data from button-0 is inserted and the error states:
adding element with duplicate id 
'__button0-container-ui5.playground.customfooteractions---Page1--page1-1

grafik grafik

stopcoder commented 1 year ago

Hello @pixel-fabian,

Thank you for sharing this finding. I've created an internal incident #2380067826. The status of the issue will be updated here in GitHub.

Regards, Jiawei