Comment 1 Karl Mikaelsson 2014-06-02 14:13:58 CEST

Chrome on iPad refused to download the certificate with "error 102". People online claim that iOS doesn't support opening files in external viewers with other browsers than Safari, but I'm not sure how accurate these comments are.

Comment 2 Samuel Mannehed 2014-06-02 16:12:26 CEST

This is considered a bug by Chrome:
https://code.google.com/p/chromium/issues/detail?id=244694

Good enough for us, we should show the link in Chrome on iOS.

Comment 3 Samuel Mannehed 2014-06-02 16:23:32 CEST

Fixed in revision 29038.

Comment 4 Henrik Andersson 2014-10-09 14:20:12 CEST

(In reply to comment #2)
> This is considered a bug by Chrome:
> https://code.google.com/p/chromium/issues/detail?id=244694
> 
> Good enough for us, we should show the link in Chrome on iOS.

Why show a link if it doesn't work ?

The upstream bug linked was fixed yesterday.

As that bug 244694 is for chromium how long does
it take to be included in chrome ?

Comment 5 Samuel Mannehed 2014-10-09 15:19:42 CEST

HTML5 client does not work in Chrome on iOS (bug 5136). It's fine as it is.

Comment 6 Henrik Andersson 2014-10-13 11:33:47 CEST

We need to handle this correctly:

The bug implies it should fix the installation of a certificate in chrome, however this doesn't work see bug 5136.

Proposal to solution for this bug is to revert the changes made, update documentation with information that chrome on iOS only works with trusted root certificates.

Comment 7 Samuel Mannehed 2014-10-13 14:02:37 CEST

(In reply to comment #6)
> We need to handle this correctly:
> 
> The bug implies it should fix the installation of a certificate in chrome,
> however this doesn't work see bug 5136.
> 
> Proposal to solution for this bug is to revert the changes made, update
> documentation with information that chrome on iOS only works with trusted root
> certificates.

Documentation was updated in r29495.

After internal discussions we decided that the changes in 29038 will not be reverted, i.e. the link will be shown on iOS no matter which browser is being used.

Comment 8 Henrik Andersson 2014-10-14 11:02:42 CEST

(In reply to comment #7)
> (In reply to comment #6)
> > We need to handle this correctly:
> > 
> > The bug implies it should fix the installation of a certificate in chrome,
> > however this doesn't work see bug 5136.
> > 
> > Proposal to solution for this bug is to revert the changes made, update
> > documentation with information that chrome on iOS only works with trusted root
> > certificates.
> 
> Documentation was updated in r29495.
> 
> After internal discussions we decided that the changes in 29038 will not be
> reverted, i.e. the link will be shown on iOS no matter which browser is being
> used.

The generated pdf looks strange, you should probably add the para in it's own <note/> than reusing the same as the other note..

Comment 9 Samuel Mannehed 2014-10-14 11:26:22 CEST

(In reply to comment #8)
> The generated pdf looks strange, you should probably add the para in it's own
> <note/> than reusing the same as the other note..

r29499

Comment 10 Henrik Andersson 2014-10-15 11:24:15 CEST

PDF looks good, closing.