Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[v4 beta-3] bug: d-print-inline causes stacking!

See original GitHub issue

This bug report here: https://github.com/twbs/bootstrap/issues/25322

was closed wrongly because it actually had 2 separate issues only one of which was fixed here:

https://github.com/twbs/bootstrap/issues/25221

The unfixed issue is related specifically to the “inline” part of the d-print-inline class.

So, while the d-print-* issue was fixed in 25221, the “inline” part of the d-print-inline class should send the inline form to the printer which does NOT happen. Instead, the form that’s being sent to the printer is stacked.

Issue Analytics

State:
Created 6 years ago
Comments:7 (3 by maintainers)

Top GitHub Comments

1reaction

bischofbcommented, Jan 16, 2018

Here is a basic code snippet where Email label appears in the same row as the email input:

<body>
    <div class="container">
    <form class="form-inline">
        <div class="form-group">
        <div class="col-sm-2">
          <label for="inputEmail3" class="form-control-label">Email</label>
        </div>
        <div class="col">
          <input type="text" class="form-control col" style="width:100%" placeholder="email">
        </div>
      </div>
    </form>
  </div>
</body>

When printing it appears as a horizontal form. bs4printhorizontal

Here is a blog post of someone that wrote up some quick CSS to fix it for BS 3 that works pretty well. Hopefully this can be done for BS 4 as well! https://blog.donnierayjones.com/2014/10/fix-bootstrap3-printing/

0reactions

mdocommented, Jan 17, 2018

Great! If you look at my referenced PR, you should be able to copy-paste from v4 to v3 some of those print style changes if you don’t want to do a full upgrade just for that.

Closing out this issue for now though since this appears resolved.