Bug 577459

Summary: Usage of MasterDetailsBlock in view or dialog
Product: [Eclipse Project] Platform Reporter: Marcus Höpfner <marcus.hoepfner>
Component: UIAssignee: Platform-UI-Inbox <Platform-UI-Inbox>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P3 CC: burcu.karlidag, marcus.hoepfner
Version: 4.23   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Marcus Höpfner CLA 2021-11-25 03:22:38 EST 
o.e.ui.forms.MasterDetailsBlock requires a ManagedForm in createContent(IManagedForm managedForm).
ManagedForm wants (or creates) a ScrolledForm. A ScrolledForm creates a Form (with FormHeading head and Composite body).

Means, when using a MasterDetailsBlock in a view or dialog all the above mentioned is created. And in the UI I see a MasterDetailsBlock with white space above. This is the form heading.

Neither SrolledForm nor Form should be subclassed (according to java doc) to overwrite this handling.

Extending ManagedForm (just with a composite instead of ScrolledForm) seems uncommon as well. At least I didn't find an implementation.


What can be done to just use a MasterDetailsBlock in others than editors (e.g. views, dialogs, wizardpages)?