Ask Questions and Find Answers

Thanks for the feedback Lee. I'll forward it to Juan, the team's designer

Thanks Jorge.

​​​​​​​The fragments are really coming on strong and the changes between what was in 7.1 and now in .2 are phenomenall.

​​​​​​​Hi Lee, many thanks again for your comments. We are embarking on a very exciting project but very challenging at the same time, we really appreciate the feedback. I answer your questions here.

• Can't "select web content" directly from link, UX path is long through series of clicks

Yes, you’re right. It is definitely something that we want to improve, we are aware that it is not very fluid

• Can't "edit web content" since menu was split in two (DXP 7.0 DE-33)

I understand that you refer to the edition of a web content that is within a fragment in the view mode. In this case, yes, this was a bug that we’ve already solved it if you check the last version of "Master". It is something that we have to review from the visual point of view but the functionality is there.

• Opacity on hover is very harsh and …
• Possibly unnesscary because the configuration icon should really be an ellipsis menu in the topper.

Very much in agreement with you, every time I see it I think the same. We wanted to make it obvious, but it doesn't have to be forced so hard.

• Configuration "icon" is inconsistent, when blank portlet it is not a menu, when content loaded it's different icon and is a menu

Yes, you’re right this is an identified bug we still have to solve.

• Fragment controls have no tooltips

Yes, we haven’t arrived there yet but we will have them

• Clicking delete ... no confirmation popup

Yes, true, We’re studying the possibility of offering a less intrusive alternative for this, as an "undo" for example, since in the context of managing multiple fragments it can become very irritating to cut the workflow with a warning message every time we delete one.

• Title of fragment in topper can go missing

Yes, it’s an identified bug we still have to solve.

Yeah it's very exciting. The fragments are really coming on strong. I would keep the widget portlet toppers and move the configuration icon into it. That would seem to solve the need for the opacity layer and allow for the widgets to be interacted with. I fear loosing the portlet topper from widgets within fragments will be a negative so would certainly advocate to leave them as is because they work really well.

I looked at the two web content menus issue, and reported the loss from 7.0
https://community.liferay.com/forums/-/message_boards/message/112633538