[ https://jira.jboss.org/jira/browse/RF-8536?page=com.atlassian.jira.plugin... ] Jay Balunas updated RF-8536: ---------------------------- Component/s: browser compatibility component-misc Assignee: Alexander Smirnov -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/RF-8536?page=com.atlassian.jira.plugin... ] Nick Belaevski reassigned RF-8536: ---------------------------------- Assignee: Nick Belaevski (was: Alexander Smirnov) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/RF-8536?page=com.atlassian.jira.plugin... ] Andrew May commented on RF-8536: -------------------------------- I've tried recreating it with the RichFaces demo webapp, but I've not been able to get the same problem to occur. Our app is using Seam 2.2.0.GA, but it's not something I can easily cut down to a runnable example. I'll see if I can create a similar test app with the same problem. I found where the script is stuck using the IE8 script debugger - it's looping waiting for an iframe to have a complete readyState: this.interval=window.setInterval(function(){if(!this.stopped){var loaded=false;var error=null;try{if(!Prototype.Browser.Opera&&!Prototype.Browser.WebKit&&this.iframe.contentWindow&&this.iframe.contentWindow.document){loaded=/complete/.test(this.iframe.contentWindow.document.readyState);}}catch(e){error=e;} if(error){this.stop();this.onerror();}} return false;}.bind(this),200); but this.iframe.contentWindow.document.readyState is always "interactive". Our fileupload looks something like this: <rich:panel id="attachmentPanel"> ... <rich:fileUpload id="attachmentUpload" fileUploadListener="#{attachments.addAttachments}" disabled="#{attachmentFailed}" listHeight="60px" maxFilesQuantity="1" noDuplicate="true" autoclear="true" acceptedTypes="#{file.types}" immediateUpload="true" ontyperejected="alert('#{messages['attachment.type.invalid']}');" onsizerejected="alert('#{messages['attachment.size.invalid']}');" onupload="setAttachable();"> <!-- Use Prototype CSS3 selector support for find and activate the last description field in an attachment table --> <a4j:support event="onuploadcomplete" reRender="attachmentPanel" oncomplete="$$('table[id$=&quot;attachmentTable&quot;] tr:last-of-type input[id$=&quot;description&quot;]')[0].activate();"/> </rich:fileUpload> <a4j:jsFunction id="setAttachableJS" name="setAttachable" ajaxSingle="true" action="#{attachments.setAttachable(attachable)}"/> It's re-rendering the whole panel after the upload completes (probably not the best idea), but I've had the same problem when changing this to only re-render the list of uploaded files (and increasing maxFilesQuantity). Sometimes it fails on the first uploaded file, sometimes after a few files have been attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/RF-8536?page=com.atlassian.jira.plugin... ] Andrew May commented on RF-8536: -------------------------------- Problem still occurs when that is removed. I've tried replacing it with a simple alert to see whether it was getting called and in the cases where the upload did not appear to complete the alert was not called. This happens whether the onuploadcomplete is in an a4j:support tag like this or directly on the rich:fileUpload tag. Something that makes the problem worse is that the stop button doesn't seem to do anything (this.stopped in the fileUpload javascript I copied above is always undefined). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/RF-8536?page=com.atlassian.jira.plugin... ] Nick Belaevski reassigned RF-8536: ---------------------------------- Assignee: Lukas Fryc (was: Nick Belaevski) I cannot reproduce the problem. Can you please try reproducing it? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/RF-8536?page=com.atlassian.jira.plugin... ] Andrew May updated RF-8536: --------------------------- Attachment: attach.txt Data from Fiddler (IE8 in compatibility mode). In Firefox I see the same sequence of requests except that there is only a single POST to /finreq/purchase/edit.jsf after the remoting calls and that returns an updated table showing the attached files - which is missing from both the IE8 responses. We have had reports of users with IE7 having attachment problems, so it may not be an IE8 only problem, but I need to verify that they're actually having the same issue and not a different problem (like picking the wrong file type or files too large). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/RF-8536?page=com.atlassian.jira.plugin... ] Lukas Fryc reassigned RF-8536: ------------------------------ Assignee: Nick Belaevski (was: Lukas Fryc) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/RF-8536?page=com.atlassian.jira.plugin... ] Nick Belaevski resolved RF-8536. -------------------------------- Resolution: Cannot Reproduce Bug Still cannot reproduce. Please provide runnable example and reopen the issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/RF-8536?page=com.atlassian.jira.plugin.syst... ] Nick Belaevski reopened RF-8536: -------------------------------- Reopening to check attached application. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/RF-8536?page=com.atlassian.jira.plugin.syst... ] Ilya Shaikovsky updated RF-8536: -------------------------------- Assignee: Konstantin Mishin (was: Nick Belaevski) Fix Version/s: 4.0.0.Milestone4 (was: Future_3.X) Component/s: component-input (was: browser compatibility) (was: component-misc) for review of inclusion possiblilities for M4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/RF-8536?page=com.atlassian.jira.plugin.syst... ] Konstantin Mishin updated RF-8536: ---------------------------------- Fix Version/s: 4.0.0.Milestone5 (was: 4.0.0.Milestone4) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira