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.

Cannot Print

See original GitHub issue

No text in the editor prints using the latest version of chrome and quill

Steps for Reproduction

Save this example html file:

<html>
    <head>
        <link href="https://cdn.quilljs.com/1.0.0-beta.11/quill.snow.css" rel="stylesheet">
    </head>
    <body>
        <div id="editor"><p>Some initial <strong>bold</strong> text</p></div>

        <script src="https://cdn.quilljs.com/1.0.0-beta.11/quill.js"></script>

        <script type="text/javascript">
          var quill = new Quill('#editor', {
            theme: 'snow'
          });
        </script>

    <body>
</html>

If you [ctrl]-[p], none of the text you enter will show up in the print preview window.

Expected behavior:

something should print

Actual behavior:

nothing prints

Platforms:

chrome 57 windows 7

Version: 1.0.0-beta.11

Issue Analytics

State:
Created 7 years ago
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

sachinrekhicommented, Aug 18, 2016

I ran into the same second page issue on print, which I solved through media queries to clean up the outputted content on print to get a nice and clean print.

I think each application will likely have to clean up the print version via media queries slightly differently given they likely want to clear chrome, other parts of their app, etc so think this might just be something each app needs to take on individually.

0reactions

jhchencommented, Aug 20, 2016

I’m generally in agreement with @sachinrekhi and am not sure what css could be added since one has to consider use cases where Quill:

taking up the whole page
takes up part of the page with the toolbar above it
takes up part of the page with toolbar detached / completely separate

In addition many production apps will probably be using one of the popular css frameworks and/or resets. If all this could be had and cover a significant portion of Quill users without diminishing the experience of others, I’m happy to take a look at a PR.