Opened 14 years ago
Closed 11 years ago
#6049 closed Bug (fixed)
Page-break marker dissapears in editor when div tag modified.
Reported by: | Burton | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | General | Version: | 3.3.1 |
Keywords: | Cc: | burtonrhodes@… |
Description
The page-break indicator that shows where the page breaks are inside the editor will not be shown if the div tag is modified with the editor (e.g. change font for the entire page).
To Recreate:
1) Input the folloing source to start. This will show a page-break indicator in the editor window.
<p> Page 1</p> <div style="page-break-after: always"> <span style="display: none"> </span></div> <p> Page 2</p>
2) Use editor: "Select All" and change font to "Arial" & size "8".
3) Toggle "Source" twice and the page-break indicator is gone.
4) Resulting HTML in the editor is below (which the editor doesn't interpret the "page-break" div tag correctly).
<p> <span style="font-size: 8px"><span style="font-family: arial, helvetica, sans-serif">Page 1</span></span></p> <p> </p> <div style="page-break-after: always"> <span style="font-size: 8px"><span style="font-family: arial, helvetica, sans-serif"><span style="display: none"> </span></span></span></div> <p> </p> <p> <span style="font-size: 8px"><span style="font-family: arial, helvetica, sans-serif">Page 2</span></span></p>
The page-break indicator should be shown even though a font attribute has been introduced to the page-break div tag.
Change History (7)
comment:1 Changed 14 years ago by
Cc: | burtonrhodes@… added |
---|
comment:2 Changed 14 years ago by
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:3 Changed 14 years ago by
Resolution: | invalid |
---|---|
Status: | closed → reopened |
As mentioned in #5079, these changes were reverted so the bug is now reproducible.
comment:4 Changed 14 years ago by
Status: | reopened → confirmed |
---|
comment:7 Changed 11 years ago by
Resolution: | → fixed |
---|---|
Status: | confirmed → closed |
Not reproducible any more.
Although I can confirm the bug in the demo, I can not reproduce it anymore on trunk duo to the changes in the page break markup that will be available in the next release (3.3.2).