PDA

View Full Version : [CLOSED][DUP][3.0.0] File upload does not work in Opera



oviksna
31 Jul 2009, 12:52 AM
Ext version tested:

Ext 3.0.0


Adapter used:

ext


css used:

only default ext-all.css


Browser versions tested against:

Opera 9.64


Operating System:

WinXP Pro


Description:

File upload function does not work in Opera.


Test Case:

Use included with Ext example file upload.


Steps to reproduce the problem:

Try included file upload example.


The result that was expected:

"Processed ..." message displayed as in other browsers.


The result that occurs instead:

Nothing is displayed
In my own code (not posted here, available if requested) submit always continues with failed function, even everything is ok.


Screenshot or Video:

none


Debugging already done:

none


Possible fix:

not provided

evant
31 Jul 2009, 1:04 AM
Can't reproduce.

I went here: http://extjs.com/deploy/dev/examples/form/file-upload.html

Typed in a name, chose a small image file and then got a success message box, Opera 9.63.

oviksna
31 Jul 2009, 1:16 AM
Tried other computer running Vista and Opera 9.63 using your link. Does not work - bug is there.

evant
31 Jul 2009, 1:20 AM
Can anyone else clarify? It works every time for me.

mjlecomte
31 Jul 2009, 7:59 AM
Did you clear your cache?

Can you post screenshot showing the error?

mystix
31 Jul 2009, 8:35 AM
tested on OSX 10.5.7, Opera 9.64.

i typed in a name, chose a small gif image, clicked Save, and no success message box.

mjlecomte
4 Aug 2009, 7:37 AM
I can reproduce. The status message dialog shows up but then vanishes without the success dialog.

I'm having a difficult time to debug using Opera's native debugger. More than half the time I can reproduce the problem, but if I set breakpoints and alerts in the right locations I can get it to work as expected.

Having a helluva time trying to figure out where/why the wheels falls off... :-?

mjlecomte
4 Aug 2009, 7:51 AM
Actually if I use the "stop at error" button, and have a breakpoint set in DataConnection


function cb(){
var me = this,
// bogus response object
r = {responseText : '',
responseXML : null,
argument : o.argument},
doc,
firstChild;

try{
doc = frame.contentWindow.document || frame.contentDocument || WINDOW.frames[id].document;
if(doc){
if(doc.body){
if(/textarea/i.test((firstChild = doc.body.firstChild || {}).tagName)){ // json response wrapped in textarea
r.responseText = firstChild.value;
}else{
r.responseText = doc.body.innerHTML;
}
}
//r.responseText still '' sometimes
//in IE the document may still have a body even if returns XML.
r.responseXML = doc.XMLDocument || doc;
}
}
...
}
The wheels fall off after that since that property can't be decoded etc.

mjlecomte
4 Aug 2009, 8:10 AM
Seems like a timing issue, depending how long I break on one of those lines the responseText may be defined as what the server sent back, might be "false", or "".

Lord
20 Aug 2009, 4:34 AM
Hi,

I get the same problem on 9.64 and 10.0 beta3, is there anything new on this topic or a workaround?

evant
20 Aug 2009, 11:03 PM
I'm going to close this issue because it's caused by the same thing as this:

http://extjs.com/forum/showthread.php?t=76659&highlight=iframe