Chroma highlighting using pygmentOptions="linenos=table" bug? about beautifulhugo HOT 4 CLOSED

Looking through this at 2PM instead of 2AM, I noticed that this appears to be a mismatch between the Chroma background-color, the border of the <td>, and the background of the page.

Is this something wrong with what I did (I haven't edited the CSS directly), with the Beautiful Hugo theme interaction with Chroma, with the Hugo core interaction with Chroma, or with Chroma itself? Perhaps Chroma doesn't generate a "full width" <tbody> and it is only noticeable when the color of the borders don't match the background of both the Chroma div and the page.

If this is the wrong place to ask for this help, please let me know. I'm still quite new to Hugo.

from beautifulhugo.

I also have this problem. My guess is that it's a Chroma problem rather than a beautifulhugo problem, but I don't have time to try to figure this out right now. If anyone figures it out, please post!

from beautifulhugo.

Is the intent that code blocks extend the full width of the post? Or is it just expected to be wide enough for the code inside?

If the expectation is that it runs the full width, then the <tbody>, <tr>, and second <td> should extend the full width and currently the only do so if the code lines are long enough.

If the expectation is that the block is only as wide as necessary to contain the code, then the issue seems to be that in the following structure, the <div class="chroma"> has a background-color but probably shouldn't. Because it does, the dark box on the far right of the image extends the entire width of the column rather than just the width of the code.

<div class="highlight">
  <div class="chroma">
    <table class="lntable">
      <tbody>
        <tr>
          <td class="lntd">
            <pre class="chroma">
              <code ...>
                <span class="lnt">
...

from beautifulhugo.

Posted question on Hugo discussion forum.

UPDATE: Looks like it is probably a Chroma issue as @nancym suggested. See comment from bep. Opened an issue with Chroma to address this.

from beautifulhugo.