Adobe Reader 9.3.1 Bug?

My OS is Ubuntu 9.10 amd64.
I found Adobe Reader 9.3.1 has a bug.
The bug is: after clicking (by mouse) the blank space of the tab bar, I can't expand any menu of the menu bar by clicking.
The blank space is shown in the following screen shot:
http://pic.pimg.tw/zxvc/4ba4274ed39fe.png?v=1269049172
Could Adobe fix this bug?

Use the forum 'Adobe Reader for Unix'.

Similar Messages

Unresolved bug in adobe reader x with non-default windows zoom level

This seems to have already been brought up here about a year ago: http://forums.adobe.com/thread/776060.
I am using Windows 7 Professional 64-bit with Firefox 12.0 and Adobe Reader 10.1.3. Here is a description of the problem:
Whenever I open any PDF file in a browser (firefox or IE) using the adobe reader I am unable to select text, save the file or interact with the content in any meaningful way because the plugin does not recognise my cursor position. If I click on some text in a PDF document, the reader will immediately highlight a region of text between where I clicked and where it thinks I started clicking from (above 20% of the screen above and to the left of where I actually clicked on the page). If I roll my mouse over the region where the dashboard normally appears, the dash does appear as intended and the cursor changes in response to hover over buttons, as if everything were working, but I am unable to click on anything (clicking does nothing). If I click and hold the dashboard when it appears, it immediately jumps to another region of the page, as if it thinks I moved the mouse (20% up and to the left again). I have recently reformatted and am now using a fresh install, and the issue remains. My desktop zoom level in windows is 150%. The problem appears only inside the browser; viewing PDFs directly in Acrobat Reader X works without issue.
I can resolve the problem either of two ways:
a) Reverting back to the default windows zoom level (125%).
b) right-clicking on the Adobe Reader X icon, navigating to the compatibility tab and clicking "Disable Display Scaling on high DPI settings"
The workaround is easy but it's disappointing that adobe hasn't fixed this. Please consider that it would mostly affect individuals who are vision impaired and might not have the know-how to resolve the problem or check for solutions online, let alone post comments such as this. As far as I can tell this problem severely impaires the functionality of adobe in any browser on any non-standard zoom windows installation.

Please be sure to post your issue in the following Feature Request/Bug Report Form.

Bug #2421120 - printing issues in Adobe Reader 9.1.3

Dear Adobe Support,
If possible I would like to know which Adobe Reader versions apart from 9.1.3 are affected by:
Bug # 2421120: When printing from Reader 9.1.3, the output is occasionally
garbled or blocks of text have characters replaced by their subsequent letter; for example, S becomes T, etc.
Thank you for your help in advance.
Brgds,
Dominik

This is not a channel to official Adobe support. I cannot find the bug by the number you gave in the Adobe help system.

Adobe Reader / Pro XI bug with PDF as embedded object in Microsoft Excel

We are using Adobe Reader and Adobe Pro version 11.0.06, Windows 7 Enterprise 64-bit, with a mixture of MS Office 2010 and 2013.
We have been able to reproduce a bug using Reader/Pro together with Excel, where Reader/Pro freezes when we preform the following tasks.
Open an Excel file where a PDF file is attached as an object in the spreadsheet
Double click and open the PDF file attached, PDF is opened in Adobe Reader/Pro
From Adobe Reader/Pro, click on the document on the Page Thumbnails, scroll the document up and down for a few times
Close the Adobe Reader/Pro, it freezes and the adobe process is starting to consume the system memory
This problem is happening on multiple machines with Adobe Reader/Pro 11.0.06 installed, regardless of the Office version and is reproducible. We did not see such issue on Adobe X.
Is there anyone reported the same?

Hello,
I know this problem was reported many months ago, but I am also experiencing this exact same issue, and have found no resolution to it yet. My user has a simple PDF embedded into an Excel 2010 document. Double click the PDF and it opens properly in Acrobat. If I close Acrobat, Excel freezes in the background (not responding). I have to force quit Excel to get back to Excel.
Also, if I double click on Acrobat again to re-open the application, it won't open. If I check Task Manager after Excel crashes, I can see that Acrobat.exe is still running in memory, and I have to force-quit it before I can re-open Acorbat.
Any progress on this issue?

Bug in Adobe Reader when displaying lines?

Hi there!
I'm creating a complex document with Apache FOP, using tables with visible and hidden borders. Although, all lines have the same attributes, Adobe Reader renders them in different thikness. In the FOP forum, there has been a lot of discussions about this issue. Conclusion is, that it is not supposed to be a FOP bug. Some other readers render the created documents well. You might want to read about it here: http://apache-fop.1065347.n5.nabble.com/Cell-border-rendering-error-thicker-with-number-co lumn-spanned-tp17999p37229.html. Displaying on screen, it is possible to avoid this by not using "Enhance thin lines". However, printed documents allways show these lines in different thikness. To avoid this being a FOP bug, there is a simple example document, producing the bug with Adobe Reader. It can be found here: http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-users/201211.mbox/raw/%3c5095C97A .[email protected]%3e/2. The document is hand crafted. To see the issue, turn on "Enhance thin lines" and try different zoom values. If this document contains incorrect contents, I'll be happy, if you let me know.
Regards.

You will not get a response from the bug report but they DO read the reports and use them to make future updates.
I notice a lot of the other issues reported here have not been responded to either.
Is that the normal process?
I haven't noticed that at all. In fact, most posts here get results as long as the poster gives enough details. Keep in mind that the answers are coming from fellow users and it is not an official avenue to contact Adobe personnel.

Bug in all Adobe Reader Updates.

Recently i have take notice of a bug in all the updates i get of Adobe Reader.
When i first installed Adobe Reader i think i can remember choosing not to create a desktop shortcut.
But whenever Adobe Reader updates, a desktop shortcut is created!
Now, as i have chosen not to have the shortcut, the fact that one is created with every single update, must clearly be a bug.
None of my other applications does this.
Is it possible with a fix? or does Adobe go the way of so many other software developers does? "It's not a bug, It's a feature!"
(bah! this was not supposed to be marked as a question, just a bit of a rant, but i'm new to the forums, so i didn't notice the option)
Message was edited by: Rofleman

Thank you for the correction.
Been a while since i did a proper install of Reader. Mostly just do silent push install on our clients.
Still don't think it is correct of the bug/update to create a desktop shortcut though...
If someone want the desktop shortcut, they most likely will have it on the desktop allready, and those who doesn't have it on the desktop, are those who have removed it, and thus most likely doesn't want it back.
So not adding the desktop shortcut would actually shrink the size of the update. Not by much, but that is irrelevant.
It's a useless thing, that doesn't need to be there.

I cannot download the uptade for adobe reader. It looks as if there is a bug. What should I do?

I cannot download the update for ad adobe reader. Why? There is a bug.

Calling it a bug doesn't make it so. More likely something is wrong on your end, but since you haven't provided any info on your system or otehr details, nobody can help you.
Mylenium

Bug? - Spaces missing when copying from Adobe Reader

I have found that when attempting to copy text from some documents (in Adobe Reader)on IOS, to paste into a writer program, that all the spaces are missing.
There is not aproblem with the same document / Adobe reader on my Windows PC.
There was also not a problem copying from the same document using another reader (ios FileBrowser native reader), then pasting.
I quick Google found that I was not alone...
https://groups.google.com/forum/#!msg/plaintext/2Bs49s1K9_o/KTwelaiqEIsJ
This link lays out the issue, not common to all IOS PDF readers, with a solution: use another reader.
Is there a solution for this in Adobe Reader, or how can it be reported to Adobe?

There are no spaces there. That is not how pdf files are constructed. HOWEVER, on PCs and Macs, the applications are smart enough to figure that spaces should be inserted into the text being copied. The iOS app is not smart enough to figure out on certain pdfs that it should insert spaces on copying from those problemsome pdfs. Adobe does have a feature request/bug reporting form where you can report the problem:
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

May 19 bug fix adobe reader app

since the bug fix, May 19 2014, I am unable to fill out pdf forms on my ipad, please help

Have you added handwritten signatures to your PDF forms in an older version of Adobe Reader for iOS before?
If so, your PDF forms were partially (and incorrectly) flattened due to a bug in Reader. The bug has been fixed in the latest version 11.3.0 (which was released on May 18, 2014).
Do you have the original PDF forms (in the state before adding the handwritten signatures)? Please fill out forms and re-apply your signatures in Reader 11.3.0. Then it should all work.
Sorry for the inconvenience.

[Bug Report!]Adobe Reader can not display 3D file normally!

I have a 3D pdf file,which is produced by Asymptote,and some labels in the 3D model, can not be displayed normally in the Adobe Reader,even the latest version 9.4.I got this file by
$asy -file pdf -render=4 file.asy
while all of them can be displayed in the OpenGL mode.
$asy -V file.asy
I hope you can give me a message about the reason and tip about how to solve the problem.
thank you very much!
code:
size(400);
import solids;
import graph3;
import three;
import math;
defaultpen(1pt+fontsize(7pt));
currentprojection=perspective(1,1,-1,up=-Z);
draw(unitsphere,palegray);//鐢荤悆
//浠ヤ笅閮ㄥ垎鐢绘敮鏌?draw(shift(1,0,0)*xscale3(0.06)*yscale3(0.06)*zscale3(1.2)*unitcylinder,palegray);
draw(shift(1,0,0)*xscale3(0.06)*yscale3(0.06)*zscale3(0.1)*unitsphere,blue);
label("1",(1.07,0,0.5),yellow);
draw(shift(-1,0,0)*xscale3(0.06)*yscale3(0.06)*zscale3(1.2)*unitcylinder,palegray);
draw(shift(-1,0,0)*xscale3(0.06)*yscale3(0.06)*zscale3(0.1)*unitsphere,blue);
label("5",(-1.07,0,0.5),yellow);
draw(shift(0,1,0)*xscale3(0.06)*yscale3(0.06)*zscale3(1.2)*unitcylinder,palegray);
draw(shift(0,1,0)*xscale3(0.06)*yscale3(0.06)*zscale3(0.1)*unitsphere,blue);
label("7",(0,1.07,0.5),yellow);
draw(shift(0,-1,0)*xscale3(0.06)*yscale3(0.06)*zscale3(1.2)*unitcylinder,palegray);
draw(shift(0,-1,0)*xscale3(0.06)*yscale3(0.06)*zscale3(0.1)*unitsphere,blue);
label("3",(0,-1.07,0.5),yellow);
draw(shift(0.707,0.707,0)*xscale3(0.06)*yscale3(0.06)*zscale3(1.2)*unitcylinder,palegray);
draw(shift(0.707,0.707,0)*xscale3(0.06)*yscale3(0.06)*zscale3(0.1)*unitsphere,blue);
label("8",(0.75,0.75,0.5),yellow);
draw(shift(-0.707,0.707,0)*xscale3(0.06)*yscale3(0.06)*zscale3(1.2)*unitcylinder,palegray);
draw(shift(-0.707,0.707,0)*xscale3(0.06)*yscale3(0.06)*zscale3(0.1)*unitsphere,blue);
label("6",(-0.75,0.75,0.5),yellow);
draw(shift(0.707,-0.707,0)*xscale3(0.06)*yscale3(0.06)*zscale3(1.2)*unitcylinder,palegray);
draw(shift(0.707,-0.707,0)*xscale3(0.06)*yscale3(0.06)*zscale3(0.1)*unitsphere,blue);
label("2",(0.75,-0.75,0.5),yellow);
draw(shift(-0.707,-0.707,0)*xscale3(0.06)*yscale3(0.06)*zscale3(1.2)*unitcylinder,palegray);
draw(shift(-0.707,-0.707,0)*xscale3(0.06)*yscale3(0.06)*zscale3(0.1)*unitsphere,blue);
label("4",(-0.75,-0.75,0.5),yellow);
draw(shift(0,0,-1.05)*xscale3(0.16)*yscale3(0.16)*zscale3(0.2)*unitcylinder,palegray);//涓婁汉瀛?draw(shift(0,0,-1.1)*xscale3(0.2)*yscale3(0.2)*zscale3(0.05)*unitcylinder,palegray);//涓婁汉瀛?draw(shift(0,0,0.85)*xscale3(0.16)*yscale3(0.16)*zscale3(0.2)*unitcylinder,palegray);//涓嬩汉瀛?draw(shift(0,0,1.05)*xscale3(0.2)*yscale3(0.2)*zscale3(0.05)*unitcylinder,palegray);//涓婁汉瀛?draw(shift(0,0,1.0)*xscale3(0.16)*yscale3(0.16)*zscale3(0.2)*unithemisphere,palegray);//涓嬩汉瀛?draw(shift(0,0,-1.05)*xscale3(0.16)*yscale3(0.16)*zscale3(0.2)*unitsphere,palegray);//涓嬩汉瀛?
path p=(1,0)..(0,1)..(-1,0)..(0,-1)..cycle;
path3 p3=path3(p);
surface sf=surface(patch(p3));
draw(shift(0,0,-1.05)*xscale3(0.2)*yscale3(0.2)*surface(sf),palegray);
draw(shift(0,0,-1.1)*xscale3(0.2)*yscale3(0.2)*surface(sf),palegray);
draw(shift(0,0,1.05)*xscale3(0.2)*yscale3(0.2)*surface(sf),palegray);
draw(shift(0,0,1.1)*xscale3(0.2)*yscale3(0.2)*surface(sf),palegray);
//浠ヤ笅缁樺埗鐜剨缂?draw(circle((0,0,sin(pi/8)),cos(pi/8)),gray);
draw(circle((0,0,sin(-pi/8)),cos(-pi/8)),gray);
draw(circle((0,0,sin(pi/4)),cos(pi/4)),gray);
draw(circle((0,0,sin(-pi/4)),cos(-pi/4)),gray);
draw(circle((0,0,sin(3pi/8)),cos(3pi/8)),gray);
draw(circle((0,0,sin(-3pi/8)),cos(-3pi/8)),gray);
xaxis3("$x$",-1.5,1.5);
yaxis3("$y$",-1.5,1.5);
zaxis3("$z$",-1.5,1.5);
surface Surf(triple center, triple A, triple B, triple C,triple D,int nu=3, int nv=nu) {
path3 p1=arc(center,A,B);
path3 p2=arc(center,B,C);
path3 p3=arc(center,C,D);
path3 p4=arc(center,D,A);
triple surf(pair t) {
real u=t.x;
real v=t.y;
path3 cr=arc(center,relpoint(p1,u),relpoint(reverse(p3),u));
return relpoint(cr,v);
return surface(surf,(0,0),(1,1),nu,nv,Spline);
real r=1+0.005;
triple A=r*unit((1,0,0.1));
triple B=r*unit((1,0,-0.1));
triple C=r*unit((-1,0,-0.1));
triple D=r*unit((-0.995,0.1,0.1));
//draw(Surf(O,A,B,C,D,4,4),yellow);
//draw(arc(O,A,B)^^arc(O,B,C)^^arc(O,C,D)^^arc(O,D,A),red+thick());
//浠ヤ笅缁樺埗閮ㄥ垎鐞冨３鏉?real r=1+0.001;
for(int i=0;i<16;++i){
triple Di_1=r*unit((sin(pi/16+i*pi/8)*cos(pi/8),cos(pi/16+i*pi/8)*cos(pi/8),sin(pi/8)));
triple Di_2=r*unit((sin(pi/16+i*pi/8)*cos(-pi/8),cos(pi/16+i*pi/8)*cos(pi/8),sin(-pi/8)));
draw(arc(O,Di_1,Di_2),gray);
for(int j=0;j<8;++j){
triple Fj_1=r*unit((sin(j*pi/4)*cos(pi/4),cos(j*pi/4)*cos(pi/4),sin(pi/4)));
triple Fj_2=r*unit((sin(j*pi/4)*cos(3pi/8),cos(j*pi/4)*cos(3pi/8),sin(3pi/8)));
draw(arc(O,Fj_1,Fj_2),gray);
triple Bj_1=r*unit((sin(j*pi/4)*cos(pi/4),cos(j*pi/4)*cos(pi/4),sin(-pi/4)));
triple Bj_2=r*unit((sin(j*pi/4)*cos(3pi/8),cos(j*pi/4)*cos(3pi/8),sin(-3pi/8)));
draw(arc(O,Bj_1,Bj_2),gray);
triple Ej_1=r*unit((sin(pi/8+j*pi/4)*cos(pi/4),cos(pi/8+j*pi/4)*cos(pi/4),sin(pi/4)));
triple Ej_2=r*unit((sin(pi/8+j*pi/4)*cos(pi/8),cos(pi/8+j*pi/4)*cos(pi/8),sin(pi/8)));
draw(arc(O,Ej_1,Ej_2),gray);
triple Cj_1=r*unit((sin(pi/8+j*pi/4)*cos(pi/4),cos(pi/8+j*pi/4)*cos(pi/4),sin(-pi/4)));
triple Cj_2=r*unit((sin(pi/8+j*pi/4)*cos(pi/8),cos(pi/8+j*pi/4)*cos(pi/8),sin(-pi/8)));
draw(arc(O,Cj_1,Cj_2),gray);
triple A_1=r*unit((sin(3pi/8)*cos(3pi/8),cos(3pi/8)*cos(3pi/8),sin(3pi/8)));
triple A_2=r*unit((sin(9pi/8)*cos(3pi/8),cos(9pi/8)*cos(3pi/8),sin(3pi/8)));
draw(arc(O,A_1,A_2),gray);
triple G_1=r*unit((sin(pi/8)*cos(-3pi/8),cos(pi/8)*cos(-3pi/8),sin(-3pi/8)));
triple G_2=r*unit((sin(11pi/8)*cos(-3pi/8),cos(11pi/8)*cos(-3pi/8),sin(-3pi/8)));
draw(arc(O,G_1,G_2),gray);
//浠ヤ笅閲囩敤鏃嬭浆鐨勬柟娉曠粯鍒惰摑鑹叉爣绀哄甫(閮ㄥ垎)
revolution belt=revolution(arc(O,1+0.006,83,0,97,0),Z,0,360);
draw(surface(belt),blue);
dot("1",r*(cos(pi/8)*cos(3pi/8),-sin(pi/8)*cos(3pi/8),sin(3pi/8)),red+0.1cm);//y鍊艰姝ｈ礋鍙樻崲锛寈y鍧愭爣瑕佹竻妤氥€?dot("2",r*(cos(9pi/8)*cos(3pi/8),-sin(9pi/8)*cos(3pi/8),sin(3pi/8)),red+0.1cm);
dot("3",r*(cos(pi/2)*cos(5pi/16),-sin(pi/2)*cos(5pi/16),sin(5pi/16)),red+0.1cm);
dot("4",r*(cos(pi/32)*cos(pi/4),-sin(pi/32)*cos(pi/4),sin(pi/4)),red+0.1cm);
dot("5",r*(cos(3pi/32)*cos(pi/4),-sin(3pi/32)*cos(pi/4),sin(pi/4)),red+0.1cm);
dot("6",r*(cos(13pi/32)*cos(pi/4),-sin(13pi/32)*cos(pi/4),sin(pi/4)),red+0.1cm);
dot("7",r*(cos(15pi/32)*cos(pi/4),-sin(15pi/32)*cos(pi/4),sin(pi/4)),red+0.1cm);
dot("8",r*(cos(17pi/32)*cos(pi/4),-sin(17pi/32)*cos(pi/4),sin(pi/4)),red+0.1cm);
dot("9",r*(cos(19pi/32)*cos(pi/4),-sin(19pi/32)*cos(pi/4),sin(pi/4)),red+0.1cm);
dot("10",r*(cos(22pi/32)*cos(pi/4),-sin(22pi/32)*cos(pi/4),sin(pi/4)),red+0.1cm);
dot("11",r*(cos(29pi/32)*cos(pi/4),-sin(29pi/32)*cos(pi/4),sin(pi/4)),red+0.1cm);
dot("12",r*(cos(19pi/16)*cos(pi/12),-sin(19pi/16)*cos(pi/12),sin(pi/12)),red+0.1cm);
dot("13",r*(cos(25pi/16)*cos(pi/12),-sin(25pi/16)*cos(pi/12),sin(pi/12)),red+0.1cm);
dot("14",r*(cos(13pi/32)*cos(pi/8),-sin(13pi/32)*cos(pi/8),-sin(pi/8)),red+0.1cm);
dot("15",r*(cos(-19pi/32)*cos(pi/8),-sin(-19pi/32)*cos(pi/8),-sin(pi/8)),red+0.1cm);
dot("16",r*(cos(-11pi/32)*cos(pi/8),-sin(-11pi/32)*cos(pi/8),-sin(pi/8)),red+0.1cm);
dot("17",r*(cos(25pi/32)*cos(pi/4),-sin(25pi/32)*cos(pi/4),-sin(pi/4)),red+0.1cm);
dot("18",r*(cos(69pi/64)*cos(pi/4),-sin(69pi/64)*cos(pi/4),-sin(pi/4)),red+0.1cm);
dot("19",r*(cos(71pi/64)*cos(pi/4),-sin(71pi/64)*cos(pi/4),-sin(pi/4)),red+0.1cm);
dot("20",r*(cos(73pi/64)*cos(pi/4),-sin(73pi/64)*cos(pi/4),-sin(pi/4)),red+0.1cm);
dot("21",r*(cos(97pi/64)*cos(pi/4),-sin(97pi/64)*cos(pi/4),-sin(pi/4)),red+0.1cm);
dot("22",r*(cos(105pi/64)*cos(pi/4),-sin(105pi/64)*cos(pi/4),-sin(pi/4)),red+0.1cm);
dot("23",r*(cos(107pi/64)*cos(pi/4),-sin(107pi/64)*cos(pi/4),-sin(pi/4)),red+0.1cm);
dot("24",r*(cos(109pi/64)*cos(pi/4),-sin(109pi/64)*cos(pi/4),-sin(pi/4)),red+0.1cm);
dot("25",r*(cos(11pi/32),0,-sin(11pi/32)),red+0.1cm);
dot("26",r*(cos(10pi/32),0,-sin(10pi/32)),red+0.1cm);
dot("27",r*(cos(pi)*cos(10pi/32),-sin(pi)*cos(10pi/32),-sin(10pi/32)),red+0.1cm);
dot("28",1.05*(G_1+3*G_2)/4,red+0.1cm);
dot("29",r*(cos(3pi/4)*cos(-pi/8),-sin(3pi/4)*cos(-pi/8),-sin(3pi/4)),red+0.1cm);

Please note that this is a user-to-user forum, and therefore not the right place to file a bug report.
Try it here instead: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

E72 V31.023 firmware-BUG in Adobe Reader LE 2.50

E72 NEW Firmware V 31.023 BUG : Cant open password protected pdf files in the updated adobe reader 2.5 LE....previous version LE 1.5 (FW Version 21.024) used to do that perfectly.Got confirmation from other users that its not working.What is the point of a firmware update ? Bringing in more bugs????
Can Nokia Revert on this...?

Its embedded, yes, but Nokia did not design the software. On further notice, since it is firmware embedded, user files, or systems files which change with usage of the phone has an effect on firmware updates.
Note that many bugs which occur after firmware updates are fixed by a hard reset+installation, meaning these bugs are user inflicted upon themselves. Files they have created, or system files created as they use the phone are apparently incompatible with the new update, rendering the installation of the update faulty.
Also firmware have been tested in Nokia labs before being send, what Nokia has no control over is the status of your phone, your PC and whatever occurs in the internet connection and lines as the data travels from the servers to your phone.
You can try to have the phone reformatted and firmware reinstalled in a Nokia Care Center as they usually get the updates in CD format, meaning these files they have are completely fine.
If you find my post helpful please click the green star on the left under the avatar. Thanks.

Bug entre Mail d'Apple et Acrobat/Adobe Reader

Bonjour,
je viens de relever un bug incroyable :
Je reçois un PDF joint dans Mail d'Apple.
Je l'ouvre (par défaut avec Acrobat sur ma machine).
Le PDF visionné n'est pas le bon !!!???!!!
En fait, en voilà la cause :
En avril 2013, je change de Mac et passe du système X 10.5 à X 10.8.
Et apparemment, les téléchargements dans Mail ne sont plus gérés dans le même dossier de "Bibliothèque" et Adobe n'a pas du relever cette modification car quelle fut ma surprise quand j'ai voulu visionner un PDF joint qui ne correspondait pas à celui qui m'a été envoyé.
Le PDF joint au mail de mon fournisseur s'appelait "DEVIS CLIENT.PDF".
Or quand je l'ouvre depuis Mail avec Acrobat Pro ou avec Adobe Reader, le fichier qui s'affiche s'appelle bien DEVIS CLIENT.PDF mais il date de mars 2013 !!???! Et ce n'est pas du tout le devis de ce fournisseur !?!
En faite, Acrobat ouvre le fichier DEVIS CLIENT.PDF qui se trouve dans Users/[moi]/Library/Mail Downloads alors que le bon fichier se trouve dans Users/[moi]/Library/Containers/com.apple.mail/Data/Library/Mail Downloads
Par contre, Aperçu m'ouvre bien le bon.
Sûrement un point à corriger de la part d'Adobe.
a+
Stéphane

J'en ai profité pour passer de la CS5 à la CC.
L'installation c'est donc faite avec Creative Cloud (le logiciel qui “manage” les applis et qui n'a pas de nom spécifique )

Can anyone help solve this frustrating drop down bug in Adobe Reader 8?

Has anyone encountered drop downs in their PDF form that don't work in Adobe Reader 8?
A simple example is my form (stripped back) here:
http://www.wikski.com/misc/test.pdf
I've built a form with 22 sections in it, some 1800 lines of code, and now every single drop down has decided to not work in Adobe Reader 8.
The behaviour is when you select a drop down, it immediately deselects itself and you can't use the element at all.
I previously had this occur, and by simply deleting the element in LiveCycle Designers ES2 (which is what I've used to create the entire form) and recreating it exactly the same; seemed to fix it. However, I am so far past the point of being able to recreate every drop down this time, I need to actually know what's causing the bug.
Any help would be greatly appreciated!
Cheers,

xfa.layout.relayout(); is required to re-render the entire form in order to have the field change color on Enter event. Without this, the field won't change color in Adobe Reader 8, this goes for all fields not just drop downs. Instead it'll just flicker the color change, xfa.layout.relayout(); makes the color change stick.
Thanks for your help, I've decided to take the set_focus() event off drop downs and keep it in place just for other field types such as the text input field.

Adobe Reader X cosmetic bug - browser integration scrollbars do not move

There appears to be a cosmetic bug in Adobe Reader X (10.0.0) browser integration. When you open a PDF in a browser window, the scroll bar remains at the top of the window when you scroll the PDF using page up / page down, or the mousewheel. If you mouse over the scroll bar, it moves to the correct place in the PDF.
This bug is consistent across IE 8, Chrome 7.0.517.44, and Mozilla Firefox 3.6.12 (running on Windows 7 Enterprise x86).

*PUSH*
Please fix this. Its just ridiculus to provide a plugin like _THE_ Adobe Acrobat Reader and not be able to implement a proper scroll behavior. Come on it can't be _that_ hard .
Thanks

Adobe Reader 2.0 unsuccessful installation - bug

Yesterday I discovered weird bug in installation of Adobe Reader for Pocket PC 2.0. Installation failed with message "installation was unsuccessful". After long investigation I found, that file "Adobe Reader User Guide.pdf" exists in "My Documents" folder (it was copied by ActiveSync synchronization). When I removed it, installation was successful. I hope it will help somebody.

bayan ayakkabı modelleri
Thanks
topuklu ayakkabılar bayan botları bayan terlikleri spor ayakkabılar erkek botları klima fiyatları led televizyon fiyatları saç şekillendirici

Adobe Reader 9.3.1 Bug?

Similar Messages

Maybe you are looking for