Multiple PDFKit highlights added
| Originator: | jdeklerk00 | ||
| Number: | rdar://34784917 | Date Originated: | October 3 2017, 8:23 AM |
| Status: | Open | Resolved: | |
| Product: | PDFKit | Product Version: | 10.13 (17A365) |
| Classification: | Bug | Reproducible: | Every time |
Area: PDFKit Summary: When adding a highlight annotation, it seems like two highlights are added over the text. When scrolling away from the page and back then the highlight works fine Steps to Reproduce: Add a PDFKit annotation with type highlight (See sample code: button1Clicked) Expected Results: Highlights are added to the PDF and the text underneath is visible Actual Results: It looks like two highlights are added and the text underneath is not visible Version/Build: 10.13 (17A365) Configuration: Sample code: I included a basic PDFView that adds Highlights to the PDF document. When Tapping on "Add Red" it adds a red highlight to page 10. Notice that the text underneath the highlight is not visible. When two-three pages away from the highlight and then back then highlight looks fine. Same with the blue button. When Adding a red/blue highlight and tapping on the "Hack" button the highlights work fine. The "Hack" button just scrolls away from the page and back to the current page
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!
Response from Apple
I talked to engineering about the bug you filed and they said that this is a known issue and they cannot recommend a better workaround than the one you mentioned in the bug. They said:
I am not able to discuss future Apple business so I cannot provide any comments about when or if this bug will be fixed. However, I recommend that you continue to test your product in future system software updates and releases to test and see if this bug has been addressed.
Regards,
John