Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Learn More

Firefox 113.0.2 cannot display .PDF fields properly.

  • 3 trả lời
  • 0 gặp vấn đề này
  • 1 lượt xem
  • Trả lời mới nhất được viết bởi jonzn4SUSE

more options

Dear Anyone

You'll laugh like drains. I've got PagePlus 9 which lets you design .PDFs with fillable fields in, the idea BEING I could send out a form which anyone could fill in in their browser without having to understand word-processing. Looked great in PagePlus 9, loaded it into Firefox and it sucked royally - fields and data all over the show. Back to the drawing board. Nearly 5 hours and countless revisions later, it still sucked royally in Firefox.

Then I tried it in Chrome, Edge, Hola and CCBrowser and it worked like an absolute dream. Displayed perfectly. Let you enter data perfectly. Put it back into Firefox and it immediately sucked blue whales through thin straws again. So it's GOT to be a hewge bug with Firefox and .PDFs. Anyone know what it is and how to handle it?

In retrospect, I, too, find it Pretty Darned Funny that I didn't think of testing it in another browser before spending 5 hours on the thing! But if it's a Firefox and PDF bug, why's nobody spotted it in Developerland? That's the bit I don't get really. (If they HAD, surely they'd've just opened up the inner workings of another browser, learned what they were doing wrong and used what they'd learned?)

Can reload it and take screenshots if requested.

Yours puzzledly

Chris.

Dear Anyone You'll laugh like drains. I've got PagePlus 9 which lets you design .PDFs with fillable fields in, the idea BEING I could send out a form which anyone could fill in in their browser without having to understand word-processing. Looked great in PagePlus 9, loaded it into Firefox and it sucked royally - fields and data all over the show. Back to the drawing board. Nearly 5 hours and countless revisions later, it still sucked royally in Firefox. Then I tried it in Chrome, Edge, Hola and CCBrowser and it worked like an absolute dream. Displayed perfectly. Let you enter data perfectly. Put it back into Firefox and it immediately sucked blue whales through thin straws again. So it's GOT to be a hewge bug with Firefox and .PDFs. Anyone know what it is and how to handle it? In retrospect, I, too, find it Pretty Darned Funny that I didn't think of testing it in another browser before spending 5 hours on the thing! But if it's a Firefox and PDF bug, why's nobody spotted it in Developerland? That's the bit I don't get really. (If they HAD, surely they'd've just opened up the inner workings of another browser, learned what they were doing wrong and used what they'd learned?) Can reload it and take screenshots if requested. Yours puzzledly Chris.

Tất cả các câu trả lời (3)

more options

Hi, can you share exemplary PDF to test this issue?

more options

Dear Ty.

Sure can, it's hilarious and you can do the test for yourself. It's when you've got a .PDF with fillable fields and you E-mail the filled-in result. It'll display the fields fine for filling-in, it can't display the E_mailed result, not nohow!

The one looking a leetle - er - disorientated(!) is my fillable .PDF in Firefox. The one looking a lot tidier's the exact same fillable .PDF, not corrected or changed in any way, in Chrome. If you want the actual .PDF to try out for yourself, tell me and I'll put it up on Mediafire for you. I created it using PagePlus 9.

I'd read there was an ongoing .PDF display problem with Firefox, after spending almost a day trying to work out why my form wouldn't display properly (and not having the brains to test a different browser before reading that!) Spent nearly all day trying to fix it for Firefox but I don't think it can be done. Firefox has a major rendering issue in it somewheres. Just an idea to end with....

We know Chrome can display it fine. Why not open Chrome up, have a look at the rendering code and see what it's doing that Firefox isn't? Surely that would speed things up, fixing-wise. It wouldn't be hacking cos Chrome's based on Chromium which is open-source anyway, isn't it? Feel free to re-contact me if there's any developments, or if I can help any other way.

Yours respectfully

Chris.

more options

Steps to replicate the issue please. Are we able to access the same pdf?