FHIR Chat · Strangeness in top navigation

Stream: IG creation

Topic: Strangeness in top navigation

Nick George (Jan 20 2022 at 19:17):

Hello - any idea why this is happening? Where are these options pulled from? image.png

Nick George (Jan 20 2022 at 19:19):

Oh found where the options are pulled from (menu.xml). Still curious about the CSS issue though!

Nick George (Jan 20 2022 at 19:24):

From the HTML, it seems a zero-width space is being inserted: Screen-Shot-2022-01-20-at-11.24.02-AM.png

Nick George (Jan 20 2022 at 19:26):

in this case our code is just

<ul xmlns="http://www.w3.org/1999/xhtml" class="nav navbar-nav">
  <li><a href="index.html">IG Home</a></li>
  <li><a href="guidance.html">Guidance</a></li>
  <li><a href="artifacts.html">Artifacts</a></li>
  <li><a href="examples.html">Examples</a></li>
  <li><a href="downloads.html">Downloads</a></li>
</ul>

Jose Costa Teixeira (Jan 20 2022 at 19:37):

that usually happens when you don't have a page artifacts.html

Jose Costa Teixeira (Jan 20 2022 at 19:37):

i.e. if the link is broken

Nick George (Jan 20 2022 at 19:40):

Hmm the link works fine

Nick George (Jan 20 2022 at 19:41):

It's listed as

          {
            "nameUrl": "artifacts.html",
            "title": "Artifacts",
            "generation": "generated"
          },

in ig.json, and just uses the stock artifacts.html as created by the ig publisher

Jose Costa Teixeira (Jan 20 2022 at 19:42):

what does your includes/menu.xml look like?

Nick George (Jan 20 2022 at 19:42):

that's the html snipped I posted in https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/Strangeness.20in.20top.20navigation/near/268744556

Nick George (Jan 20 2022 at 19:44):

Artifacts is the only page that's not generated from markdown or html... not sure if "generated"is the right generation code to use there

Jose Costa Teixeira (Jan 20 2022 at 19:45):

ah that

Jose Costa Teixeira (Jan 20 2022 at 19:46):

html

Jose Costa Teixeira (Jan 20 2022 at 19:46):

it's confusing but the page is generated by the template so the publisher see it as just another html

Nick George (Jan 20 2022 at 19:47):

Ah ok. And then it seems the artifacts page itself generates its own navbar? and doesn't pull in menu.xml? is there a way to make that consistent?

Nick George (Jan 20 2022 at 19:48):

hmm changing to html didn't fix it :(

Nick George (Jan 20 2022 at 19:49):

oh hold on that might have been a mistake

Nick George (Jan 20 2022 at 19:51):

Yup that worked (and fixed the other question about the artifacts navbar). Thanks! (Some kind of error message would be nice rather than rendering wrong!)