WickedPdf CSS rule `page-break-after: avoid` does not work as expected












0















I want the page to not break between two divs. When I assign the CSS rule page-break-after: avoid or page-break-before: avoid, it simply does not work, but if I assign set page-break-before: always, it works perfectly, can anyone help me?



Here is the code and result:



The html code with page break props



page breaking between divs










share|improve this question





























    0















    I want the page to not break between two divs. When I assign the CSS rule page-break-after: avoid or page-break-before: avoid, it simply does not work, but if I assign set page-break-before: always, it works perfectly, can anyone help me?



    Here is the code and result:



    The html code with page break props



    page breaking between divs










    share|improve this question



























      0












      0








      0








      I want the page to not break between two divs. When I assign the CSS rule page-break-after: avoid or page-break-before: avoid, it simply does not work, but if I assign set page-break-before: always, it works perfectly, can anyone help me?



      Here is the code and result:



      The html code with page break props



      page breaking between divs










      share|improve this question
















      I want the page to not break between two divs. When I assign the CSS rule page-break-after: avoid or page-break-before: avoid, it simply does not work, but if I assign set page-break-before: always, it works perfectly, can anyone help me?



      Here is the code and result:



      The html code with page break props



      page breaking between divs







      html css ruby-on-rails printing wicked-pdf






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 27 '18 at 17:22









      Unixmonkey

      15k44259




      15k44259










      asked Nov 22 '18 at 12:15









      João BoscoJoão Bosco

      126




      126
























          1 Answer
          1






          active

          oldest

          votes


















          0














          I think what you are looking for is page-break-inside: avoid;, not before or after.



          That rule should be applied to a wrapping container that you want to avoid page breaks inside, however it is ultimately up to the browser to decide. If you want to help make sure there is enough room, it can be helpful to also apply page-break-before: always;, to ensure the element you don't want to break starts at the top and has a lot of space.






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53430810%2fwickedpdf-css-rule-page-break-after-avoid-does-not-work-as-expected%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            I think what you are looking for is page-break-inside: avoid;, not before or after.



            That rule should be applied to a wrapping container that you want to avoid page breaks inside, however it is ultimately up to the browser to decide. If you want to help make sure there is enough room, it can be helpful to also apply page-break-before: always;, to ensure the element you don't want to break starts at the top and has a lot of space.






            share|improve this answer




























              0














              I think what you are looking for is page-break-inside: avoid;, not before or after.



              That rule should be applied to a wrapping container that you want to avoid page breaks inside, however it is ultimately up to the browser to decide. If you want to help make sure there is enough room, it can be helpful to also apply page-break-before: always;, to ensure the element you don't want to break starts at the top and has a lot of space.






              share|improve this answer


























                0












                0








                0







                I think what you are looking for is page-break-inside: avoid;, not before or after.



                That rule should be applied to a wrapping container that you want to avoid page breaks inside, however it is ultimately up to the browser to decide. If you want to help make sure there is enough room, it can be helpful to also apply page-break-before: always;, to ensure the element you don't want to break starts at the top and has a lot of space.






                share|improve this answer













                I think what you are looking for is page-break-inside: avoid;, not before or after.



                That rule should be applied to a wrapping container that you want to avoid page breaks inside, however it is ultimately up to the browser to decide. If you want to help make sure there is enough room, it can be helpful to also apply page-break-before: always;, to ensure the element you don't want to break starts at the top and has a lot of space.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 27 '18 at 17:28









                UnixmonkeyUnixmonkey

                15k44259




                15k44259
































                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53430810%2fwickedpdf-css-rule-page-break-after-avoid-does-not-work-as-expected%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    'app-layout' is not a known element: how to share Component with different Modules

                    android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

                    WPF add header to Image with URL pettitions [duplicate]