Bug 377567 - Some annotation not visible in Google Chrome PDF viewer
Summary: Some annotation not visible in Google Chrome PDF viewer
Status: RESOLVED DUPLICATE of bug 383651
Alias: None
Product: okular
Classification: Applications
Component: PDF backend (show other bugs)
Version: 1.0.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-13 17:19 UTC by Kieran Ramos
Modified: 2017-09-13 04:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
PDF annotated in okular (1.09 MB, application/pdf)
2017-03-13 18:38 UTC, Kieran Ramos 		Details
PDF annotated in Adobe Reader DC (1.36 MB, application/pdf)
2017-03-13 18:39 UTC, Kieran Ramos 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Kieran Ramos 2017-03-13 17:19:33 UTC 
Inline notes, polygons, stamps, and underlines that are created in Okular version 1.0.2 on openSUSE tumbleweed or Okular 0.25.0 on Ubuntu 16.04 are not visible in the chrome web browser's built-in PDF viewer. The inline notes, though invisible, can be seen by hovering your mouse over the note, it will then pop up. Underlines are sometimes shown, but not completely. Polygons and stamps don't appear at all.

As expected all annotations display properly in Okular and in Adobe Reader DC.
Comment 1 Luigi Toscano 2017-03-13 17:39:48 UTC 
If they show properly in Adobe Reader DC (which is kind of reference implementation), couldn't it be an issue of the library/rendering engine used by chromium?

Also, a sample file would help.
Comment 2 Kieran Ramos 2017-03-13 18:38:29 UTC 
Created attachment 104540 [details]
PDF annotated in okular
Comment 3 Kieran Ramos 2017-03-13 18:39:13 UTC 
Created attachment 104541 [details]
PDF annotated in Adobe Reader DC
Comment 4 Kieran Ramos 2017-03-13 18:41:12 UTC 
(In reply to Luigi Toscano from comment #1)
> If they show properly in Adobe Reader DC (which is kind of reference
> implementation), couldn't it be an issue of the library/rendering engine
> used by chromium?
> 
> Also, a sample file would help.

Yes, I suspect it could be an issue with chromium, but the same PDF annotated similarly in Adobe Reader DC does appear fine in chrome. Is there some other way we could test to be certain if its chromium or okular?
Comment 5 Nate Graham 2017-09-13 04:50:40 UTC 
Related to or a duplicate of https://bugs.kde.org/show_bug.cgi?id=383651
Comment 6 Nate Graham 2017-09-13 04:51:04 UTC 

*** This bug has been marked as a duplicate of bug 383651 ***