Disparity in Editing Web Content between Widget and Content Pages

• Type: Bug
• Status: Closed
• Resolution: Duplicate
• Affects Version/s: 7.2.10 DXP FP2, 7.2.10 DXP FP3, 7.2.X, 7.2.1 CE GA2, Master
• Fix Version/s: None
• Component/s: Content Display Widgets > Web Content Display widget, Fragment Administration
• Labels: None
• Fix Priority: 4

If the goal is to eliminate widget pages, we need content pages to level up in UX. Currently web content in a content page behaves very differently to what users have learned.

Steps
1) Create a widget page add a web content widget and some content
2) Note that hovering over content brings up various menus mainly in the portlet topper
3) This topper is missing from content pages in non-edit mode

See GIF

 

Expected
Interaction to match 1:1 between content and widget pages that contain web content.

Actual
Content pages are harder to use, no UX department anywhere in the world wants to create products that are even harder to use.