Bug 187077

Summary: When trying to print a very long email on iOS, the print preview is blank
Product: WebKit Reporter: Tim Horton <thorton>
Component: New BugsAssignee: Tim Horton <thorton>
Status: RESOLVED FIXED    
Severity: Normal CC: aestes, commit-queue, darin, timothy
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch none

Tim Horton
Reported 2018-06-26 19:27:26 PDT
When trying to print a very long email on iOS, the print preview is blank
Attachments
Patch (2.20 KB, patch)
2018-06-26 19:27 PDT, Tim Horton 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Tim Horton
Comment 1 2018-06-26 19:27:36 PDT
Created attachment 343677 [details] Patch
Tim Horton
Comment 2 2018-06-26 19:27:48 PDT
rdar://problem/41107013
WebKit Commit Bot
Comment 3 2018-06-27 01:27:47 PDT
Comment on attachment 343677 [details] Patch Clearing flags on attachment: 343677 Committed r233250: <https://trac.webkit.org/changeset/233250>
WebKit Commit Bot
Comment 4 2018-06-27 01:27:48 PDT
All reviewed patches have been landed. Closing bug.
Darin Adler
Comment 5 2018-06-28 09:13:23 PDT
Comment on attachment 343677 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=343677&action=review > Source/WebKit/ChangeLog:11 > + ChildProcessProxy::sendSync has a (surprising) default timeout of 1 second, Should we now also change that default to either "no default" or to "infinity" for clarity?
Tim Horton
Comment 6 2018-07-02 11:57:26 PDT
(In reply to Darin Adler from comment #5) > Comment on attachment 343677 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=343677&action=review > > > Source/WebKit/ChangeLog:11 > > + ChildProcessProxy::sendSync has a (surprising) default timeout of 1 second, > > Should we now also change that default to either "no default" or to > "infinity" for clarity? Probably infinity, since everything else defaults to that, but it's a bit scary. I filed https://bugs.webkit.org/show_bug.cgi?id=187259.
Note You need to log in before you can comment on or make changes to this bug.