Databases
StackOverflow2013
Postsdbo
PONo uploaded photo display in Mac browsers?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PONo uploaded photo display in Mac browsers?
    text
    copied!<p>I am totally stumped on this...Using the asyncUpload and swfUpload JS plugins to have users upload a photo. After upload, the photo is displayed in a little area. Works perfect on any Windows browser, but no go on any Mac browser. So weird. I've narrowed it down to this piece:</p> <pre><code> // Called when upload completed successfully (puts success details into hidden fields) upload_success_handler: function (file, response) { $("input[name$=_filename]", container).val(file.name); $("input[name$=_guid]", container).val(response); $("span[id$=_completedMessage]", container).html("&lt;img class='uploader' src='/public/assets/logos/{0}{1}' /&gt;&lt;br /&gt;" .replace("{0}", response) .replace("{1}", file.type) ); }, </code></pre> <p>Here's what Firebug is saying is generated in a Mac browser (FF 3.6.13 in particular):</p> <pre><code>&lt;span id="photo_completedMessage" style="display: inline;"&gt; &lt;img class="uploader" width="0" height="0" src="/public/logos/66764b72-ad65-44b3-8c08-e74c24ee1356JPEG"&gt; &lt;br&gt; &lt;/span&gt; </code></pre> <p>So the GUID's being generated, and it's sort of finding the file type? But not placing it as an extension or something? If I type it in manually in the Bug, it shows up fine, so it's finding the image on the server. I'm lost. Help appreciated. Again, this is ONLY on ANY Mac browser. IE, Chrome, FF, Safari on Windows all work fine.</p> <p>EDIT - Here's the Windows Firebug code:</p> <pre><code>&lt;span id="photo_completedMessage" style="display: inline;"&gt; &lt;img class="uploader" width="203" height="285" src="/public/logos/66764b72-ad65-44b3-8c08-e74c24ee1356.jpg"&gt; &lt;br&gt; &lt;/span&gt; </code></pre>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload