-
24 Jan 2012 3:59 AM #1
FileUploadField browse button invisibly extends beyond "Browse..." Button boundaries
FileUploadField browse button invisibly extends beyond "Browse..." Button boundaries
Hi!
Adding a FileUploadField, the area with which I can open the file browse dialog extends to the right of the button. The FileUploadField shows shows this behavior under Firefox 9.01 and Chrome 16.0.912.75 m. IE 8 works fine.
Example:
On the following screenshot (code above) I have a button placed to the right. If I click this button, the file selection dialog opens.Code:<container:HorizontalLayoutContainer height="24"> <container:child layoutData="{innerHorizontalLayout}"> <form:FormPanel ui:field="masterLanguagePackSourceForm" method="POST" encoding="MULTIPART" action="cgitranslator/uploadService"> <form:FieldLabel text="Language Pack"> <form:widget> <form:FileUploadField ui:field="masterLanguagePackSourcePath" /> </form:widget> </form:FieldLabel> </form:FormPanel> </container:child> <container:child> <button:TextButton ui:field="masterLanguagePackSourceUploadButton" text="Upload" /> </container:child> </container:HorizontalLayoutContainer>
capture_005_24012012_124624.jpg
Under Opera 11.60, the browse button is vertically shifted down (see following screenshot), otherwise functionality as expected.
capture_006_24012012_125310.jpg
Best Regards,
Peter
-
12 Mar 2012 2:05 AM #2
This bug is still open in beta 4. It can be verified under
http://staging.sencha.com:8080/examp...ace:fileupload
If you click to the right of the browse button, the file selection dialog opens. If you place a button to this position, also the file selection dialog opens and the button positioned there is not triggered.
Best Regards,
Peter
-
12 Mar 2012 9:56 AM #3
Thanks for the report. I've been able to replicate this behaviour locally, so I've filed a ticket against the team. I'll post a reply here with any changes we make.
-
29 Jun 2012 12:49 AM #4
This bug is still not fixed in 3.0.0b Commercial.
-
28 Jan 2013 8:34 AM #5
I've run into this bug as well. Does anyone have a workaround?
You found a bug! We've classified it as
EXTGWT-1617
.
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.


Reply With Quote