PDF viewer: Browser compability

[reginafcompton]

The PDF viewer does not behave as expected in some browsers.

Edge browser

The embedded PDF pane is blank. Printing from the embedded PDF is also blank.

Chrome 69.0.3497.92, os x el capitan 10.11.6

[hancush]

so i'm seeing this again in chrome and firefox, but it resolves when i refresh the page. if it's important, the events i'm viewing all have new documents, i.e., those documents are not yet in the cache. in the console, there is a message about cross-origin resource sharing. these docs suggest we can remedy this issue (or at least the manifestation i'm seeing) by adding an nginx directive.

[hancush]

update: having dealt with a similar issue in #433, i'm pretty confident this is related to cors. we use flask-cors in the property-image-cache application to add the appropriate headers, so that may not be working as expected. if it is working as expected, then there may be something wonky going on how we're requesting and displaying the document on the councilmatic side. if it's the latter, then this may be addressed by swapping the library we use to render pdfs, as outlined in #294 (comment).

[hancush]

hmmmmm mozilla/pdf.js#4530 (comment)

[hancush]

S3ResponseError: S3ResponseError: 403 Forbidden
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>B469F9930C08BD93</RequestId><HostId>cZQ1GD4VPshpbYfR4oRZpmdcTe4ix4UJksSEMtN927A3sC6FPPkPFQQjV48QlEbLmkfrYftP45o=</HostId></Error>

hmmmmmmm https://sentry.io/organizations/datamade/issues/973621844/?project=64504&query=is%3Aunresolved

mmmmmm
https://stackoverflow.com/questions/10854095/boto-exception-s3responseerror-s3responseerror-403-forbidden
mmmmm

[hancush]

i went into the aws iam console and gave the pic user permission to set the acl on existing objects. then, i followed the instructions here #443 (comment) to remove an event agenda from the cache, and tried to visit the page again to replicate this issue. hark, things behaved as expected!

[hancush]

@shrayshray i believe i've solved this! any objection to closing?

[shrayshray]

Okay to close, things seem to be working as expected. Thanks!