Openui5: titleChanged Event not propagating across nested components correctly

[grahamrobbo]

This issue is the same as #2959 - I have supplied a working demo that shows the issue I am seeing as requested by @flovogt

OpenUI5 version: 1.80.0

Browser/version (+device/version): Chrome Version 84.0.4147.89 (Official Build) (64-bit)

Any other tested browsers/devices(OK/FAIL): None tested

Steps to reproduce the problem:

1. Clone repo https://github.com/grahamrobbo/titleChanged_event to access via local HTTP server
   Note how the root component manifest.json contains the following in the sap.ui5.routing.targets section.

            "targets": {
                ...,
                "suppliers": {
                    "type": "Component",
                    "usage": "suppliersComponent"
                },
                "categories": {
                    "type": "Component",
                    "usage": "categoriesComponent"
                },
                "products": {
                    "type": "Component",
                    "usage": "productsComponent",
                    "title": "Dummy Title"
                },
                ...
            }

Note that "products" component target has title property set to "Dummy Title" while the other component targets do not have the title property set.

1. Load app and navigate to the supplier component.

Note titleChanged event has been propagated so that page title is now set to "Supplier List" from the supplier component manifest.json file.

Now refresh page while still on routing hash #/suppliers. (Might need to clear cache)

Note that titleChanged event did not propagate so the page title remains "Component Based Navigation Demo".

Now navigate to the "Products" component - the component that has the title property set in the root component manifest.json - and try the same test.

Note that page title is always updated as expected using the setting from the product component manifest.json file.

[flovogt]

Hi @grahamrobbo ,
Thank you for sharing this finding. I've created an internal incident 2080344993. The status of the issue will be updated here in GitHub.
All the best,
Florian

[flovogt]

Hi @grahamrobbo,
this issue is fixed with c1e5ee4 and will be available with UI5 version 1.83.0.
Thanks a lot for reporting this finding.
Florian