I recently upgraded from 2017r3 to 2022 and today performed the first build of the primary target - a HTML5 target (a help docs site). I then copied the output folder to a localhost folder and viewed the localhost in my browser. That's how I test the output before I publish it.
Problem:
So, my problem is that one of the stylesheets is being output in the wrong precedence order in the HTML. After a day of investigating and comparing it to the source code of the live project (the previous release), I have worked out part of the reason behind this, but have not worked out where this change came from. It wasn't me...! I wonder if any of you have experienced the same thing? I also wonder if it might be a bug.
Illustration:
The following shows you the <link rel="stylesheets"> output generated today by Flare 2022. (These are just the ones relevant to this problem) Note the position of xa_help_styles.css - it's first.
Code: Select all
<link href="../resources/stylesheets/xa_help_styles.css" rel="stylesheet" type="text/css" />
<link href="../resources/stylesheets/xa_mega_menu.css" rel="stylesheet" type="text/css" />
<link href="../resources/stylesheets/xa_styles.css" rel="stylesheet" type="text/css" />
<link href="../resources/stylesheets/scrollbar.css" rel="stylesheet" type="text/css" />
Code: Select all
<link href="../resources/stylesheets/xa_mega_menu.css" rel="stylesheet" />
<link href="../resources/stylesheets/xa_styles.css" rel="stylesheet" />
<link href="../resources/stylesheets/scrollbar.css" rel="stylesheet" />
<link href="../resources/stylesheets/cookieconsent.min.css" rel="stylesheet" />
<link href="../resources/stylesheets/xa_help_styles.css" rel="stylesheet" />
And, xa_help_styles.css is associated with the Project and the Primary Target.
Am I wrong, or is Flare v2022 treating the stylesheet attached to my master pages in /master-pages/page-layout-example.flmsp as if it were a local?
Is it the case that back in version 2017, the master-pages files '.flmsp' were granted lower precedence? What's going on?
I can fix this by simply adding the desired stylesheet to the master pages, but I'd like to know why this is now required in v2022.