Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-122068

As a Site Creator, I want admin controls to be isolated from my customizations

    Details

      Description

      Traditionally, Liferay has offered Themes as a solution to customize the experience and visual appearance of a site. While this works well in many cases, it presents unique challenges as well, being the most recurring the fact that UI administration controls inadvertently change as well, making themes harder to produce.

      This is an obvious but unfortunate consequence of how HTML and CSS work, which makes applying styles really prone to bleeding into undesired components and causing undesired effects.

      Below can be seen one a common approach to get the right styling for components and pages:

      The goal of this task is to provide a mechanism to isolate administration interfaces from changes in a Liferay Theme.

      We initially tried a similar approach with As an admin, I want to be able to deploy CSS and JS that affect all sites and pages independently of their theme. In there we focused on making sure that some CSS was always applied regardless of the theme. That approach differs from now in that if theme does not apply to components, we would not need to apply CSS on top to overwrite what the themes do.

      Acceptance Criteria

      • Specific administration components are not affected by the site theme
      • Administration interfaces are always presented using the same (admin/classic) theme
      • DXP offers a way for widget/taglib creators to mark their applications and components as "isolated"

      Test Information section

      Test Scenarios:

      Requirement Test Case Covered by frontend/backend unit test? (Yes/No) Test Priority (business impact) Chrome
      Pass/Fail
      Firefox
      Pass/Fail
      Specific administration components are not affected by the site theme Given portal running with either of the Product Menu/Control Menu/Add Panel/Simulation Menu/Page Audit/Page Editor Toolbar CSS component is used with the cadmin wrapper
      When the theme of the site is changed
      Then the CSS of the component will not change
      no 5-critical    
        Given portal running with Style Book Editor CSS used with the cadmin wrapper
      When the theme of the site is changed
      Then the CSS of the Style Book Editor will not change
      no 4-major    
        Given portal running with Toast Alerts used with the cadmin wrapper
      When the theme of the site is changed
      Then the CSS of the Toast Alerts will not change
      no 4-major    
        Given portal running with Theme Portlet Topper used with the cadmin wrapper
      When the theme of the site is changed
      Then the CSS of the Theme Portlet Topper will not change
      no 4-major    
        Given portal running with Admin Modals used with the cadmin wrapper
      When the theme of the site is changed
      Then the CSS of the Admin Modals will not change
      no 4-major    
        Given portal running with Page Editor Sidebar CSS used with the cadmin wrapper
      When the theme of the site is changed
      Then the CSS of the Page Editor Sidebar CSS will not change
      no 4-major    
        Given portal running with Dropdown Menu used with the cadmin wrapper
      When the theme of the site is changed
      Then the CSS of the Dropdown Menu will not change
      no 4-major    
        Given portal running with Applications Menu used with the cadmin wrapper
      When the theme of the site is changed
      Then the CSS of the Applications Menu will not change
      no 4-major    
        Given portal running with Tooltips/Popovers/Alerts CSS used with the cadmin wrapper
      When the theme of the site is changed
      Then the CSS of the Tooltips/Popovers/Alerts will not change
      no 4-major    
        Given portal running with Page Editor Inline Controls used with the cadmin wrapper
      When the theme of the site is changed
      Then the CSS of the Page Editor Inline Controls will not change
      no 4-major    
      Administration interfaces are always presented using the same (admin/classic) theme Given clean instance of portal with no theme applied
      When a theme is applied to the site
      Then the admin interface is presented as default theme
      no 5-critical    
      DXP offers a way for widget/taglib creators to mark their applications and components as "isolated" Given portal admin component code in editor
      When class= 'cadmin' is applied to a component
      And When a theme is applied to the component
      Then the admin component will have it's default theme
      no 5-critical    
        Given portal admin component code in editor
      When class= 'cadmin' is applied to a component
      And When a user applies CSS changes higher than cadmin component
      And When a theme is applied to the component with the applied CSS
      Then the admin component will have it's CSS changed
      no 4-major    

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              support-lep@liferay.com SE Support
              Reporter:
              jose.balsas Chema Balsas
              Recent user:
              John Co
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:

                  Packages

                  Version Package