FLUID-4382: Blank screen on Uploader demo from the build site when using IE9 Windows 7

Description

steps to reproduce:
1. Use IE9 on a Windows 7 machine, loads up http://build.fluidproject.org/infusion/demos/uploader/html/uploader.html
2. Get blank screen.

Environments

Windows 7 Professional IE 9, Service Pack 1
64x machine
No flash installed on IE9

Comments

• Harris Wong commented 2011-07-29T09:47:55.605-0400

  Log messages:
  -------------------------------------------------------------------------
  LOG: 09:33:26.278: Resolving demands for function names fluid.transformOptions in context of component fluid.uploader
  LOG: 09:33:26.278: Components in scope for resolution:
  { typeName: "fluid.uploader" id: 3vptys63-5}
  { typeName: "fluid.dynamicEnvironment" id: 3vptys63-4}
  { typeName: "fluid.instantiator" id: 3vptys63-7}
  { typeName: "fluid.staticEnvironment" id: 3vptys63-2}
  { typeName: "fluid.browser" id: 3vptys63-3}
  LOG: 09:33:26.281: Beginning instantiation of component with name "uploaderContext" as child of { typeName: "fluid.uploader" id: 3vptys63-5}
  LOG: 09:33:26.282: Resolving demands for function names fluid.progressiveCheckerForComponent,uploaderContext in context of component fluid.uploader
  LOG: 09:33:26.282: Components in scope for resolution:
  { typeName: "fluid.uploader" id: 3vptys63-5}
  { typeName: "fluid.dynamicEnvironment" id: 3vptys63-4}
  { typeName: "fluid.instantiator" id: 3vptys63-8}
  { typeName: "fluid.staticEnvironment" id: 3vptys63-2}
  { typeName: "fluid.browser" id: 3vptys63-3}
  LOG: 09:33:26.282: No matches found for demands, using direct implementation
  LOG: 09:33:26.297: Resolving demands for function names fluid.transformOptions in context of component fluid.progressiveCheckerForComponent
  LOG: 09:33:26.298: Components in scope for resolution:
  { typeName: "fluid.progressiveCheckerForComponent" id: 3vptys63-9} - path: uploaderContext
  { typeName: "fluid.uploader" id: 3vptys63-5}
  { typeName: "fluid.dynamicEnvironment" id: 3vptys63-4}
  { typeName: "fluid.instantiator" id: 3vptys63-8}
  { typeName: "fluid.staticEnvironment" id: 3vptys63-2}
  { typeName: "fluid.browser" id: 3vptys63-3}
  LOG: 09:33:26.315: Resolving demands for function names fluid.transformOptions in context of component fluid.progressiveChecker
  LOG: 09:33:26.315: Components in scope for resolution:
  { typeName: "fluid.uploader" id: 3vptys63-5}
  { typeName: "fluid.dynamicEnvironment" id: 3vptys63-4}
  { typeName: "fluid.instantiator" id: 3vptys63-8}
  { typeName: "fluid.staticEnvironment" id: 3vptys63-2}
  { typeName: "fluid.browser" id: 3vptys63-3}
  LOG: 09:33:26.316: Finished instantiation of component with name "uploaderContext" as child of { typeName: "fluid.uploader" id: 3vptys63-5}
  LOG: 09:33:26.316: Beginning instantiation of component with name "uploaderImpl" as child of { typeName: "fluid.uploader" id: 3vptys63-5}
  LOG: 09:33:26.317: Resolving demands for function names fluid.uploaderImpl,uploaderImpl in context of component fluid.uploader
  LOG: 09:33:26.318: Components in scope for resolution:
  { typeName: "fluid.uploader" id: 3vptys63-5}
  { typeName: "fluid.uploader.singleFile" id: 3vptys63-11} - path: uploaderContext
  { typeName: "fluid.dynamicEnvironment" id: 3vptys63-4}
  { typeName: "fluid.instantiator" id: 3vptys63-8}
  { typeName: "fluid.staticEnvironment" id: 3vptys63-2}
  { typeName: "fluid.browser" id: 3vptys63-3}
  LOG: 09:33:26.318: Located 3 potential matches, selected best match with 2 matched context names: [object Object]
  LOG: 09:33:26.337: Resolving demands for function names fluid.transformOptions in context of component fluid.uploader.singleFileUploader
  LOG: 09:33:26.338: Components in scope for resolution:
  { typeName: "fluid.uploader.singleFileUploader" id: 3vptys63-12} - path: uploaderImpl
  { typeName: "fluid.uploader" id: 3vptys63-5}
  { typeName: "fluid.uploader.singleFile" id: 3vptys63-11} - path: uploaderContext
  { typeName: "fluid.dynamicEnvironment" id: 3vptys63-4}
  { typeName: "fluid.instantiator" id: 3vptys63-8}
  { typeName: "fluid.staticEnvironment" id: 3vptys63-2}
  { typeName: "fluid.browser" id: 3vptys63-3}
  LOG: 09:33:26.340: Finished instantiation of component with name "uploaderImpl" as child of { typeName: "fluid.uploader" id: 3vptys63-5}

• Harris Wong commented 2011-07-29T12:52:31.490-0400

  Uploader.js line 733:
  toggleVisibility($(that.options.selectors.basicUpload), that.container);

  $(that.options.selectors.basicUpload) => null
  that.options.selectors.basicUpload => ".fl-progEnhance-basic"

  why is it returning a null?

• Harris Wong commented 2011-07-29T13:21:45.014-0400

  I did a $('body').html() after uploader is initialized, i don't see the basic html markup included in the container. I looked at the uploader demo, and saw the following, https://github.com/harriswong/infusion/blob/master/src/webapp/components/uploader/html/Uploader.html#L50,

  It seems like "flc-uploader fl-uploader" are only applying to the multi file uploader but excluding the single file uploader. Should there be a container that wraps both the singleFile and multieFile uploader with class="flc-uploader fl-uploader" instead?

• Colin Clark commented 2011-07-29T14:19:19.618-0400

  Hi Harris,

  The single file upload controls should be in a separate container from the full Uploader's markup. Here's the code in question:

  https://github.com/harriswong/infusion/blob/master/src/webapp/components/uploader/js/Uploader.js#L730-735

• Mike Lam commented 2011-09-19T13:39:05.989-0400

  Same bug as FLUID-4444 which has now been resolved.