RESOLVED CONFIGURATION CHANGED12716
Assertion failure involving printing and display:run-in and dt/dl elements; overlapping text on Release build
https://bugs.webkit.org/show_bug.cgi?id=12716
Summary Assertion failure involving printing and display:run-in and dt/dl elements; o...
John Sullivan
Reported 2007-02-09 14:47:50 PST
This is in Radar as <rdar://problem/4988325> To reproduce: 1. Load the attached example page, which is a reduced version of the one in radar 4960095/bugzilla 12449 2. Command-P to bring up Print dialog 3. Click Preview button Usually the assertion failure happens here. But sometimes, I have to repeat steps 2 and 3. I've never had to repeat them more than once to hit the assertion failure, in many attempts, so I'm marking this repro always. On a release build the printed page shows overlapping, doubly-drawn text, and the web page redraws to show that same bad appearance. See the attached screenshot. There don't seem to be any other symptoms on a release build -- reloading takes the page back to normal, and subsequent pages aren't messed up.
Attachments
Test case (270 bytes, text/html)
2007-02-09 14:48 PST, John Sullivan
no flags
Screenshot of overlapping text (3.55 KB, image/png)
2007-02-09 14:50 PST, John Sullivan
no flags
Reduction (does not require printing) (186 bytes, text/html)
2007-02-09 16:04 PST, mitz
no flags
John Sullivan
Comment 1 2007-02-09 14:48:50 PST
Created attachment 13094 [details] Test case Test case used to demonstrate the problem.
John Sullivan
Comment 2 2007-02-09 14:50:04 PST
Created attachment 13095 [details] Screenshot of overlapping text Screenshot that shows the results after printing, on a Release build (where the assertion doesn't fire)
mitz
Comment 3 2007-02-09 16:04:28 PST
Created attachment 13099 [details] Reduction (does not require printing) The bug is that a style recalc resets the isInline() flag of the run-in to false.
mitz
Comment 4 2008-02-28 13:19:41 PST
See also bug 12522.
Alexey Proskuryakov
Comment 5 2024-04-24 15:40:47 PDT
This doesn't reproduce in Safari 17.5 beta.
Note You need to log in before you can comment on or make changes to this bug.