Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-17819

Create test to assert number of CSS imports on a Confluence page

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Timed out
    • None
    • None
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      In CONF-17151, it was established that if a page contains more than 32 CSS imports, IE will randomly drop CSS files and/or JavaScript includes, causing random and difficult-to-debug failures.

      The implemented fix batched up the CSS imports for the bundled plugins, reducing the number of import statements, but is not a permanent solution to the problem.

      We should have a test that asserts that the default number of CSS imports on any given Confluence page is less than a defined number (possibly around 20, which gives buffer room for 3rd-party plugins to include their own). Thus, a few years down the track when we all forget and the number of CSS imports creeps up again, we'll see a test failure before we start seeing random JavaScript errors in IE.

      Created as a separate issue from CONF-17151, as writing the automated test is a lower priority task that shouldn't delay the release process.

              barconati BillA
              pwyatt Penny Wyatt (On Leave to July 2021)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: