Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-53669

Importing an External Style Sheet is not working in Style Macro

XMLWordPrintable

      Summary

      When using Style Macro, importing an external style sheet is not working. Defining a Stylesheet appears to be working.

      Environment

      Confluence Cloud: 1000.81.0

      Steps to Reproduce

      1. Edit a page.
      2. Click Insert > Other Macros
      3. Select the Style Macro
      4. Specify a URL to import an external stylesheet
      5. Save the page.

      Expected Results

      • The custom style sheets is not being applied when using the import parameter in Style Macro

      Actual Results

      • The custom style sheets should be applied when using the import parameter in Style Macro

      Notes

      • Tested in Confluence Server 5.9.4 and it works fine.

      Workaround

      • Define a Style Sheet instead of Importing an External Style Sheet.

            [CONFCLOUD-53669] Importing an External Style Sheet is not working in Style Macro

            Sunny Xu (Inactive) made changes -
            Resolution New: Timed out [ 10 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]

            Sunny Xu (Inactive) added a comment -

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!

            Sunny Xu (Inactive) added a comment - Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team!
            Sunny Xu (Inactive) made changes -
            Labels Original: affects-cloud cc-platform style-macro New: affects-cloud cc-platform stale-bulk-close202011 style-macro

            Charisma Riley added a comment -

            Being able to import an external stylesheet, for those that use them, is essential. No one wants to have to maintain in-page stylesheets to maintain overall corporate style; that's a ridiculous premise, as there is no way to update them all in bulk. External style sheets are expected at my org and, honestly, expected industry-wide for designers expected to know them. They post ZERO security risk, especially embedded into 12+ iframes, as you've built out in the Cloud editor. Especially because on-prem do not have this restriction. And ESPECIALLY because you are re-including it into your new Premium offering. How not okay is that? We signed on because of many of these features you keep removing only to re-include them to Premium and NOT removing them from on-prem. Why??

            Charisma Riley added a comment - Being able to import an external stylesheet, for those that use them, is essential. No one wants to have to maintain in-page stylesheets to maintain overall corporate style; that's a ridiculous premise, as there is no way to update them all in bulk. External style sheets are expected at my org and, honestly, expected industry-wide for designers expected to know them. They post ZERO security risk, especially embedded into 12+ iframes, as you've built out in the Cloud editor. Especially because on-prem do not have this restriction. And ESPECIALLY because you are re-including it into your new Premium offering. How not okay is that? We signed on because of many of these features you keep removing only to re-include them to Premium and NOT removing them from on-prem. Why??
            Michael Andreacchio made changes -
            Status Original: Needs Triage [ 10030 ] New: Gathering Impact [ 12072 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2368554 ] New: JAC Bug Workflow v3 [ 3405154 ]
            Status Original: Open [ 1 ] New: Needs Triage [ 10030 ]
            Bugfix Automation Bot made changes -
            Support reference count Original: 3 New: 4
            Shannon S made changes -
            Link New: This issue is related to CONFCLOUD-53128 [ CONFCLOUD-53128 ]
            SET Analytics Bot made changes -
            Support reference count Original: 1 New: 3
            SET Analytics Bot made changes -
            Support reference count Original: 3 New: 1

              Unassigned Unassigned
              jalor Janice Alor (Inactive)
              Affected customers:
              2 This affects my team
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: