Problem/Motivation

Some of the projects using UI Styles use the good old Manage Display instead of Layout Builder for some displays.

Proposed resolution

Let's expose UI Styles to manage display.

Comments

pdureau created an issue. See original summary.

grimreaper’s picture

grimreaper
Primary language French
Location France 🇫🇷
commented

Should it be ui_styles_manage_display or ui_styles_field_formatter?

pdureau’s picture

pdureau commented
Title: Add ui_styles_manage_display sub module » Add ui_styles_field_formatter sub module

You are right Grimrepaer, let's stop thinking about config entities and their backoffice UI but about plugins.

grimreaper’s picture

grimreaper
Primary language French
Location France 🇫🇷
commented

https://www.drupal.org/project/fences allows to control wrappers tag and/or remove wrappers. It also allows to inject classes. Maybe working with this module will do the trick.

pdureau’s picture

pdureau commented
Title: Add ui_styles_field_formatter sub module » [2.x] Add ui_styles_field_formatter sub module
Status: Active » Postponed

Moved to 2.X because target a plugin and not config entity.

https://www.drupal.org/project/fences allows to control wrappers tag and/or remove wrappers. It also allows to inject classes. Maybe working with this module will do the trick.

Fences target field.html.twig, a "wrapper" template which may be ignored by next gen display builders (experience_builder & display_builder) and deprecated with ThemeManager::render()

grimreaper’s picture

grimreaper
Primary language French
Location France 🇫🇷
commented
Issue tags: +ddd2025
grimreaper’s picture

grimreaper
Primary language French
Location France 🇫🇷
commented
Status: Postponed » Closed (won't fix)

field.html.twig wrapper ignored by UIP2 and Display Builder.

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.