Skip to content
← Share your feedback on Acrobat DC

Settings and activity

1 result found

  1. Regression in Adobe Acrobat Chrome extension - verified and reproducible

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    4 comments  ·  Adobe Acrobat in Browsers » Adobe Acrobat in Chrome  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Raymond Davey commented  · 

    I have one further diagnostic result which may be useful.

    In Chrome's DevTools for the Acrobat extension, under Extension Storage → Local, I found:

    'mimeHandlerEnabled = "true"'
    'mimeCohort = "master"'

    As a test, I changed only:

    'mimeCohort = "chromeMimeHandler"'

    I then repeated exactly the same POST-generated PDF report with Acrobat extension 26.8.1.5 still enabled.

    The problem disappeared and the PDF displayed correctly.

    So on the same machine, browser, extension version and application:

    'mimeCohort = "master"' → POST PDF triggers the additional GET and fails

    'mimeCohort = "chromeMimeHandler"' → POST PDF displays correctly

    There is one further potentially important observation: the change to 'mimeCohort' does not persist.

    If I reload the application page from which the report is generated, the Acrobat extension automatically changes 'mimeCohort' back from '"chromeMimeHandler"' to '"master"'. Once it has reverted to '"master"', the original problem returns.

    So '"chromeMimeHandler"' is only a temporary diagnostic change. Something in the normal extension/page flow is actively setting the cohort back to '"master"'.

    This appears to provide a reproducible A/B test of the problem without changing the application, browser or extension version.

    Hopefully this gives the engineering team a useful pointer as to where the regression may be occurring.

    An error occurred while saving the comment
    Raymond Davey commented  · 

    Further note. I have just tested the same machine with the Edge browser.

    This extension works fine in Edge. Extension version 26.7.1.0

    I do note that this is an older version of the extension. The most recent update is not available in the Edge browser store

    I compared HAR captures between the working and failing versions.

    Adobe extension 26.7.1.0 in Edge: the POST receives a 200 application/pdf response and no further request is made to the PDF URL. The PDF displays correctly.

    Adobe extension 26.8.1.5 in Chrome: the same POST receives a 200 application/pdf response, but immediately afterwards a new GET request is made to the identical POST-only URL. That GET fails.

    This suggests a possible change/regression in how 26.8.1.5 handles PDFs returned directly from POST requests.

    An error occurred while saving the comment
    Raymond Davey commented  · 

    Version 26.8.1.5 does not fix the issue

    I have a clean HAR file for you if you contact me directly

    Can also set you up with a test case (in a live system) for you to diagnose

    All other extensions are disabled. This is a clean browser session under Chrome

    Raymond Davey shared this idea  ·