Openui5: Bad visualization of NotificationListItem inside a Dialog in belize theme

[cadupper]

OpenUI5 version: 1.40.6

Browser/version (+device/version): Chrome 53.0.2785.116 m

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

URL (minimal example if possible):
http://pastebin.com/cjYw71cQ

User/password (if required and possible - do not post any confidential information here):

Steps to reproduce the problem:

1. Create a dialog with a fragment contains a list of NotificationListItem
2. Expand the message

What is the expected result?
show the expandend text inside the dialog

What happens instead?
The text comes out from the dialog

Any other information? (attach screenshot if possible)
Right expansion with bluecrystal

Bad expansion with belize

[TobiasOetzel]

Hi,

i wasnot able to reproduce the issue in my bin
did i miss something?

best regards,
tobias

[cadupper]

I have the same problems with a simple List inside a Dialog

Dialog are always fragmens in my app and I open it by simple code...

ui5bp.summaryTinteArticleManager.summaryDialog = sap.ui.xmlfragment("ui5bp.view.fragment.SummaryTinteArticleDialog", this); ui5bp.summaryTinteArticleManager.summaryDialog.open();

[TobiasOetzel]

Hi,

with just a screenshot this will be impossible to reproduce. Please try to adjust my bin.
An xmlfragment is a mere factory function and does not add anything to the created instances.

the way you propagate models is very strange and also is going on UI5 internal properties.
Please use the depentent mechanism that is described here

this.getView().addDependent(this._oDialog);

best regards,
Tobias

[cadupper]

If I set a a fixed height by contentHeight="500px" the problem magically vanishes

[TobiasOetzel]

Seems to be fixed on your end so i am closing this.

Best regards,
Tobias

[TobiasOetzel]

We were able to reproduce the issue in an internal system
Seems to affect other dialogs and is not specific to Notification list item

Chrome only issue and a painting issue of the browser.

Reopening it. Tracked 1670467393

[marinparushev]

Hello,

the issue has been fixed and the fix is/will be available from versions 1.40.10 and 1.42.2 or higher.

Regards,
Marin Parushev