Issue 65446 in chromium: Please implement form submit in internal PDF viewer.

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2 Area-Undefined

New issue 65446 by wbustraan: Please implement form submit in internal PDF
viewer.
http://code.google.com/p/chromium/issues/detail?id=65446

Chrome Version : 8.0.552.215
URLs (if applicable) : http://prototype.d1mg.com/pdftest/search-post.pdf
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5: OK (with Adobe Reader plugin)
Firefox 3.x: OK (with Adobe Reader plugin)
IE 7/8: OK (with Adobe Reader plugin)

What steps will reproduce the problem?
1. Go to form with submit button (you may use
http://prototype.d1mg.com/pdftest/search-post.pdf)
2. Enter data in the text box.
3. Click the submit button.

What is the expected result?
The browser should submit data as application/x-www-form-urlencoded to the
URL specified in the submit button
(http://prototype.d1mg.com/pdftest/dump-post.php in the example)

What happens instead?
There is no effect when using the new internal PDF viewer.

Don't get me wrong, I love the new PDF internal viewer, but this will break
any site that relies on this functionality. I know that the internal viewer
can be disabled, but we don't really want to have to tell our users to do
that, since the internal viewer is so fast.

AcroForms are part of the PDF 1.2 standard, it should be supported.

[chro...@googlecode.com]

Comment #3 on issue 65446 by MatthewD...@gmail.com: Please implement form

submit in internal PDF viewer.
http://code.google.com/p/chromium/issues/detail?id=65446

I work for a company that has set up thousands of submittable PDF forms for
clients in the last several years. With the growing popularity of this
browser and its inability to process forms properly, the frustration our
clients face continues to increase. We are working resolve issues on a
case-by-case which essentially require using other methods, but this is not
something we can implement all-at-once for every client. If the PDF Viewer
had the ability to properly submit PDF forms, this would save a lot of
frustration.

Granted, the same problem exists in Safari's built in PDF Viewer for Apple
computers. The popularity of Safari does not appear to be growing as vastly
as Chrome.

[chro...@googlecode.com]

Comment #4 on issue 65446 by jim.he...@formrouter.com: Please implement

form submit in internal PDF viewer.
http://code.google.com/p/chromium/issues/detail?id=65446

We have the same problem (with Mac also as a previous comment stated). The
simplest solution may be to implement a tiny piece of javascript
functionality and allow us to use:
app.viewerType
app.alert

app.viewerType would be set to something like "Chrome Plug-in" and
app.alert would allow us to display a message letting the user know that
for this particular PDF you need to open it in Acrobat.

[chro...@googlecode.com]

Comment #9 on issue 65446 by eldimen...@gmail.com: Please implement form

submit in internal PDF viewer.
http://code.google.com/p/chromium/issues/detail?id=65446

It's been nearly 2 years, why is this not working yet?

[chro...@googlecode.com]

Comment #10 on issue 65446 by buster.de: Please implement form submit in

internal PDF viewer.
http://code.google.com/p/chromium/issues/detail?id=65446

Please, at least fix output of app.viewerType as mentioned in comment #4.
Current output is a boolean "true", that doesn't help at all. So it is not
possible to inform users with an app.alert().

[chro...@googlecode.com]

Comment #11 on issue 65446 by john.zar...@gmail.com: Please implement form

submit in internal PDF viewer.
http://code.google.com/p/chromium/issues/detail?id=65446

Any updates, we are a healthcare firm that relies on PDF submission for
several workflow processes. This shortcoming forces us to stay on Internet
Explorer. Who wants to be restricted?

[chro...@googlecode.com]

Comment #12 on issue 65446 by jnc.n...@gmail.com: Please implement form

submit in internal PDF viewer.
http://code.google.com/p/chromium/issues/detail?id=65446

I work for the City of SF and we have the same issue. We're getting around
the vagaries of browsers by using a web-based solution that works on any
browser and OS. There is a cost for this approach but it's not that
expensive.

http://www.radpdf.com/

**Disclosure**
I don't have any relationship to this company other than being a customer
through my work at the City of SF.

[chro...@googlecode.com]

Comment #14 on issue 65446 by boud...@gmail.com: Please implement form

submit in internal PDF viewer.
http://code.google.com/p/chromium/issues/detail?id=65446

We are using PDF form to submit orders by our customers. This is quite big
issues for them and us with ing popularity of Chrome. Is there any progress
with this bug?

[chro...@googlecode.com]

Comment #15 on issue 65446 by boud...@gmail.com: Please implement form

submit in internal PDF viewer.
http://code.google.com/p/chromium/issues/detail?id=65446

We are using PDF form to submit orders by our customers. This is quite big

issue for them and us with growing popularity of Chrome. Is there any
progress with this bug? thanks

[chro...@googlecode.com]

Comment #16 on issue 65446 by quintile...@googlemail.com: Please implement

form submit in internal PDF viewer.
http://code.google.com/p/chromium/issues/detail?id=65446

I too have the issue that Chrome is only submitting the fields on the same
page as the submit button (in FDF format).

[chro...@googlecode.com]

Comment #17 on issue 65446 by Kyt...@gmail.com: Please implement form

submit in internal PDF viewer.
http://code.google.com/p/chromium/issues/detail?id=65446

We have tested this bug extensively, and have discovered that Chrome is, in
fact, submitting the PDF form in FDF format (another documented bug since
the PDF specifies XFDF, which is the format every other browser sends),
HOWEVER...while Chrome is running the php page the FDF is submitted to, it
is NOT displaying them.

Using the Chrome developer tool, I can see that the php is not at fault,
and is loading just fine. When I double click on the php document in the
developer tool, the page displays just perfectly. However, in normal usage,
when I click Submit on the PDF form in Chrome, the user never leaves the
PDF page. The php runs in the background, and submits the form to our
database, but it just won't leave the PDF page.

Please make this a priority! I, too, am a PDF provider, and I have NO
control over my user settings. As popular as Chrome is now, this really
needs to be addressed, please!

I'll gladly supply any screenshots or code snippets requested.

[chro...@googlecode.com]

Comment #18 on issue 65446 by gjwater...@gmail.com: Please implement form

submit in internal PDF viewer.
http://code.google.com/p/chromium/issues/detail?id=65446

I work for local government and can confirm that this is an issue for us as
well.

Our logs show that the submit is successfully posting to our handler from
Chrome's built-in PDF viewer, however, the built-in viewer does not
redirect. We use the redirect to bring our users to a confirmation page
where one can enter a captcha, an e-mail address, etc. It is a required
step in the workflow. The Chrome end-users are left thinking that the
button does nothing and either call to complain, or, give up on the form.

Frankly, it would be better for our users if there were no built-in PDF
viewer in Chrome, as now we have to explain to the users why their PDF
viewer is not in fact the right PDF viewer. As local government, many of
our customers are elderly and not computer savvy, and thus it's difficult
to walk them through the distinction between Chrome's built in PDF viewer
and Adobe's Acrobat Reader.

Please up the priority on resolving this if possible.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Comment #23 on issue 65446 by k.conway...@gmail.com: Please implement form

submit in internal PDF viewer.
http://code.google.com/p/chromium/issues/detail?id=65446

Absolutely agree with #18 and #19. Serious issue and problem in Government.

[chro...@googlecode.com]

Comment #26 on issue 65446 by videoj...@gmail.com: Please implement form

submit in internal PDF viewer.
http://code.google.com/p/chromium/issues/detail?id=65446

I am an officer at the local level for the Knights of Columbus. We have
about 1.9 million members, and as with any organization with 100+ years of
longevity, lots of paperwork. This is an absolute deal breaker for me. I
have used Chrome since about the beginning when it first came out, and now
when I have to do my work as a Knight of Columbus, I simply have to abandon
Chrome. I hate to use IE-- I HATE it-- But I can't do what I need to do in
Chrome without significant machinations. Please, Please, PLEASE fix this
issue. The Knights of Columbus Supreme website actually cause a pop-up to
warn me every single time I go to the page to even download a form, warning
me that Chrome has a bug in it. I am so sad to be reminded that so often
that Chrome has a major bug in it.

I know this looks like a "+1 me too" post, but I think it is significant
with regard to the population that this affects.

[chro...@googlecode.com]

Comment #27 on issue 65446 by ryan.m...@landgate.wa.gov.au: Please

implement form submit in internal PDF viewer.

https://code.google.com/p/chromium/issues/detail?id=65446

Is the Chrome PDF plugin built on PDFium?
Should this issue be raised under that project instead?

I've searched their bug tracker and found nothing about this. :(

https://bugs.chromium.org/p/pdfium/issues/list
https://groups.google.com/forum/#!forum/pdfium
https://groups.google.com/forum/#!forum/pdfium-bugs

[chro...@googlecode.com]

Updates:
Labels: -Mstone-X -Cr-Internals -Cr-Blink OS-All

Comment #28 on issue 65446 by the...@chromium.org: Please implement form

submit in internal PDF viewer.
https://code.google.com/p/chromium/issues/detail?id=65446

re: comment 27 - yes, and no.

[chro...@googlecode.com]

Comment #29 on issue 65446 by the...@chromium.org: Please implement form

submit in internal PDF viewer.
https://code.google.com/p/chromium/issues/detail?id=65446

The original test PDF link for this bug is dead. Does anyone else have an
example to test with?

[chro...@googlecode.com]

Comment #30 on issue 65446 by ryan.m...@landgate.wa.gov.au: Please

implement form submit in internal PDF viewer.
https://code.google.com/p/chromium/issues/detail?id=65446

http://larimer.org/workforce/lcycc_energy_application_2011.pdf
http://www.cafcn.ca/PDFs/2013-online-conference-registration-form.pdf
http://www0.landgate.wa.gov.au/docvault.nsf/web/PS_MAPS_FORMS/$file/Geospatial_Data_Request.pdf

[chro...@googlecode.com]

Comment #31 on issue 65446 by ryan.m...@landgate.wa.gov.au: Please

[chro...@googlecode.com]

Comment #32 on issue 65446 by ryan.m...@landgate.wa.gov.au: Please

implement form submit in internal PDF viewer.
https://code.google.com/p/chromium/issues/detail?id=65446

Some more examples:

http://www.pdfscripting.com/public/FreeStuff/PDFSamples/DynamicEmail_AcroForm.pdf
http://www.pdfscripting.com/public/FreeStuff/PDFSamples/DynamicEmail_XFAForm.pdf

[chro...@googlecode.com]

Comment #34 on issue 65446 by the...@chromium.org: Please implement form

submit in internal PDF viewer.

https://code.google.com/p/chromium/issues/detail?id=65446

From the ones listed in comments 30 and 32, I tried:

http://larimer.org/workforce/lcycc_energy_application_2011.pdf

and found that it actually works if one fills in the signature field at the
bottom. If I edit the PDF by hand to change the POST URL to a web server I
control, I can see the POST going through.

I also tried:

http://www0.landgate.wa.gov.au/docvault.nsf/web/PS_MAPS_FORMS/$file/Geospatial_Data_Request.pdf

and that does not work, either because there's form validation that's
failing, or because the file contains XFA forms. (See bug 62400)

I didn't even try:

http://www.pdfscripting.com/public/FreeStuff/PDFSamples/DynamicEmail_XFAForm.pdf

because it has XFA in the name.

And I looked at:

http://www.pdfscripting.com/public/FreeStuff/PDFSamples/DynamicEmail_AcroForm.pdf

which actually triggers the email client via mailto: but does not have the
data attached because mailto: does not support attachments. Thus PDFs with
email submission may never work.

[chro...@googlecode.com]

Comment #35 on issue 65446 by j...@mfi.net: Please implement form submit in

internal PDF viewer.
https://code.google.com/p/chromium/issues/detail?id=65446

Are you kidding me, here's Google Chrome that can't or won't fix this
problem. Come on guys. Get my submit button to work. Please. Help!!!