#6832 closed Bug (invalid)
improper page-break plugin
Reported by: | yiminghe | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | General | Version: | 3.4.3 |
Keywords: | Cc: |
Description
page-break is not only used when printing ,but mostly it is used by backend program to split a long post for paging.
steps :
1.set the following code to editor :
<div style="border: 10px solid green;"> <p> 123456</p> </div>
2.put cursor between '3' and '4' ,and click page-break button, code generated by current version:
<div style="border: 10px solid green;"> <p> 123</p> <div style="page-break-after: always;"> <span style="display: none;"> </span></div> <p> 456</p> </div>
if the backend program splits it without html parsing , then each part of its content is malformed
so i think page-break should generate such code :
<div style="border: 10px solid green;"> <p> 123</p> </div> <div style="page-break-after: always;"> <span style="display: none;"> </span></div> <div style="border: 10px solid green;"> <p> 456</p> </div>
and above code is better for printing and splitting .
Attachments (3)
Change History (5)
Changed 14 years ago by
Attachment: | before.png added |
---|
Changed 14 years ago by
Changed 14 years ago by
Attachment: | 6832.patch added |
---|
comment:1 Changed 14 years ago by
Resolution: | → invalid |
---|---|
Status: | new → closed |
Note that page-break is a page media only feature, which should impose at all no DOM structure deconstruction, with you proposition, a table will never have a chance to get spread over two transparencies (same as with other elements).
Instead, imposing that server-side content division based on page-break feature is simply wrong, please, just create the proper plugin to do that, editor core being incapable of handling such a luggage.
comment:2 Changed 11 years ago by
Keywords: | page-break removed |
---|
patch from trunk