[ObjectPage]: Multiple unnecessary photo request calls are made

[Brahmansh]

Describe the bug

Unnecessary photo request calls are made every time we click on Collapse header button or scrolldown when header is collapsed.

Isolated Example

No response

Reproduction steps

1. Go to https://ui5.github.io/webcomponents-react/v2/?path=/story/layouts-floorplans-objectpage--default
2. Open devtools, Collapse header and observe GET request call made for photo.
3. Now expand header and collapse again, observe photo request call made again
4. Or scrolldown when header collapses, observe photo request call made again

Expected Behaviour

Multiple GET calls for photo request shouldn't be made every time header collapses.

Screenshots or Videos

No response

UI5 Web Components for React Version

2.18.0

UI5 Web Components Version

2.18

Browser

Chrome

Operating System

No response

Additional Context

No response

Relevant log output

Organization

No response

Declaration

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

[Lukas742]

Hi @Brahmansh

could you please elaborate on why you see this bug? Typically resources should be cached after being loaded the first time. In the storybook example there will be no duplicate GET request, if caching is active. Only if you disable caching you will see multiple requests.

We could prevent this behavior, but in this case we would have to always mount both images (the small one in the title-area and the large one in the header-area). So, I would like to understand why the current behavior is a problem on your end, before we change our implementation.

Additionally, even if caching is disabled, you can cache the image on the application side, for example by fetching it once and storing it in memory or by using a blob URL.

[Brahmansh]

In some of our environments we have response headers with Cache-Control: no-store, where it makes GET request every time header collapses. So, I think it would be better to be handled from webcomponents side.

[ui5-webcomponents-react-bot]

🎉 This issue has been resolved in version v2.18.1 🎉

The release is available on v2.18.1

Your semantic-release bot 📦🚀