VMware {code} Community
ChrisSmith2
Enthusiast
Enthusiast
Jump to solution

vSphere 7.0U3 UI regressions for custom objects

vSphere 7.0U3 has made further UI changes, and in the process seems to have introduced a nasty regression for plugins using custom objects.

The "Actions" menu (and right-click menu from VMware-provided lists) for custom objects renders incorrectly - the container is not sized correctly, so the text for each line in the menu wraps, typically causing each word to appear on a separate line - this looks horrendous. There are other inconsistencies - the font is much larger than that used for VMware-provided objects, and the general styling is different (e.g. the menu header) - but those are not a severe as the wrapping issue.

 

Reply
0 Kudos
1 Solution

Accepted Solutions
stoevm
VMware Employee
VMware Employee
Jump to solution

Hi Chris,

I did a little bit of research and it turns out that this was fixed on our main branch, however it did not reach the vSphere 7.0U3 release. It will be released with an upcoming version of the vSphere.

Thanks,
Martin

  

View solution in original post

Reply
0 Kudos
7 Replies
stoevm
VMware Employee
VMware Employee
Jump to solution

Hi Chris,

Can you share a screenshot of where exactly this issue is hit ?
Also an example plugin.xml extension if possible.

Thanks,
Martin

Reply
0 Kudos
ChrisSmith2
Enthusiast
Enthusiast
Jump to solution

I've sent you a PM with screenshots showing the same Actions menu from the same plugin under 6.7U3n and 7.0U3, as well as the same ESXi host Actions menu under each. I've also provided the "plugin.xml" from the actual plugin.

Reply
0 Kudos
chrissmith1
Enthusiast
Enthusiast
Jump to solution

Martin - did you receive the PM, and were you able to confirm the regressions shown in the screenshots? Can you provide any update on this issue?

Reply
0 Kudos
stoevm
VMware Employee
VMware Employee
Jump to solution

Hi Chris,

I did a little bit of research and it turns out that this was fixed on our main branch, however it did not reach the vSphere 7.0U3 release. It will be released with an upcoming version of the vSphere.

Thanks,
Martin

  

Reply
0 Kudos
ChrisSmith2
Enthusiast
Enthusiast
Jump to solution

This is still broken in 7.0U3a (7.0.3.00100).

Reply
0 Kudos
ChrisSmith2
Enthusiast
Enthusiast
Jump to solution

This is still broken in 7.0U3b (which still reports itself as 7.0.3.00100 in the "About VMware vSphere" page of the UI).

Reply
0 Kudos
stoevm
VMware Employee
VMware Employee
Jump to solution

Hi Chris,

The fix did not get into the 7.0U3 release cycle.
I can say for sure that it will be included in the next non-patch release.

Sorry for the inconvenience that this bug introduced,
Martin 

Reply
0 Kudos