break-after : page; not working in Safari 17 When the printing process is carried out, the page cannot be made into 2 or more pages
Created attachment 469032 [details] screenshoot while print in Safari 17 when use break-after:page;
Created attachment 469034 [details] naive test case, not reproducing the issue
Thank you for the report. I cannot reproduce this with the above test case. Could you please provide steps to reproduce that we could follow, including a test case at a publicly accessible URL?
(In reply to Alexey Proskuryakov from comment #3) > Thank you for the report. I cannot reproduce this with the above test case. > > Could you please provide steps to reproduce that we could follow, including > a test case at a publicly accessible URL? https://klinikrespirasimalang.com/pdf/tampil.php?f=resep1-16398-AlanLukitoGunawan.pdf&t=resep This is a website that I created to display PDF results and print them. When printed, it should produce 2 pages. For other browsers it can still use this code, but for Safari 17 it can't, the output is like the one in the attached image above.
Thank you! I can reproduce in iOS 17.2, and this works correctly in iOS 16.7.2. I can also reproduce on macOS. It looks like page break happens correctly, but positioning the content on the paper is wrong, so the second page is partly printed on the first sheet. Additionally (and it may need a separate investigation), I sometimes only get one page on print preview, not two. Please keep the test page up for investigation, as we don't have a reduced test case yet.
<rdar://problem/119669466>
(In reply to Alexey Proskuryakov from comment #5) > Thank you! I can reproduce in iOS 17.2, and this works correctly in iOS > 16.7.2. I can also reproduce on macOS. > > It looks like page break happens correctly, but positioning the content on > the paper is wrong, so the second page is partly printed on the first sheet. > > Additionally (and it may need a separate investigation), I sometimes only > get one page on print preview, not two. > > Please keep the test page up for investigation, as we don't have a reduced > test case yet. That's right, previously it wasn't a problem, then one of the users updated iOS to version 17 and then this case appeared For other users can still use this code