JQuery attr function to replace image src not working in browsers except Chrome

Hi all,

As per title, I believe there are a lot people who face this problem when want to dynamically update an image using JQuery.
Once there is a requirement for this, the first thing come out in mind is the .attr() function provided by JQuery. The code roughly will be like this:

$('#<image element id>').attr('src',<new image source>);

Logically this should be done the job. However, after a test in several browsers, one will find out that this only working in Chrome. Internet Explorer, Firefox and Safari do not perform as expected.
Why will this happen? It is due to cache issue.
The solution for this issue is very simple. It is just needed to append a timestamp behind the new image source to trick the browser that the image is a new one for each time the function is triggered.
It is as below:

$('#<image element id>').attr('src', <new image source>?' + new Date().getTime());
* the part highlighted in yellow is the additional part to add into the code.

Refresh your browser and try dynamically change the image again. It should be working this time. :)

Happy coding!!!

Comments

  1. UnknownAugust 10, 2015 at 4:57 AM

    this is not working in chome
    var navbar_logo = $('.navbar-logo img');
    src = navbar_logo.data('logo-dark')+'?'+new Date().getTime();
    navbar_logo.attr('src', src);

    ReplyDelete
  2. UnknownJune 23, 2016 at 10:12 AM

    its not working
    $('#blah').attr('src', e.target.result+'?' + new Date().getTime());
    }

    ReplyDelete

Post a Comment

Popular posts from this blog

Django Form: MultipleChoiceField and How To Have Choices From Model Example

Image
Its been long time after my last post. During my development in Django, I encountered this issue, where I don't know how to assign tuple value to choice argument in Django MultipleChoiceField. So here I would like to share on how to do this. Here are some information on the environment for this code: Django 1.6.1 doc: https://docs.djangoproject.com/en/1.6/ref/forms/fields/#multiplechoicefield Then looks into the forms.py: #1 import the models which use for MultipleChoiceField from TestChoice.models import Test #2 create a static CHOICES variable to hole this tuple, you can perform any normal Django query here. TEST_CHOICES = [[x.id, x.name] for x in Test.objects.all()] #3 If you would like to add extra choices, then you can do the following: TEST_CHOICES.insert(0, ['', "Empty"]) #4 The form field should looks like below, (required=False, only if you want this field to be optional) class TestForm(forms.Form):     test= forms.MultipleChoiceField
Read more

Jquery Validation fix for date format dd/mm/yyyy in Chrome and Safari

After a long search, finally i found the solution for JQuery validation ( Can get the plugin from here:   http://docs.jquery.com/Plugins/Validation ) for date in Chrome and Safari. This is because Chrome and Safari do not handle the format properly. When developer set datepicker format from mm/dd/yyyy (default format) to dd/mm/yyyy , JQuery validation plugin tool does not able validate this format (only happen in Chrome and Browser. Other browser like IE, and Firefox is working fine). For example, if you initiate datepicker like this: $(':input.date').datepicker({dateFormat: 'dd/mm/yy'}); Then when you select date with day more than 12 like 13/11/2011 or 22/11/2011 and so on, and when you are using Jquery validation plugin to validate before submit, this will normally return with ' Please enter a valid date ' in Chrome and Safari. The solve this issue, it is needed to modify JQuery validation plugin. For my case it is jquery.validation.min.js. Lo
Read more

DJango Queryset comparing date time

Good day to all developers. Today encountered this issue where I do a simple queryset in DJango and hit with the following warning message:   RuntimeWarning: DateTimeField MessageContent.send_time received a naive datetime (2014-05-14 04:46:30.392000) while time zone support is active. How is this happen? This is due to I do the following datetime comparison in my queryset: import datetime Item.objects.filter(created = datetime.datetime.now()) The error is due to TIME_ZONE (in settings.py) is enabled by default. So the solution for this is pretty simple: 1) Either to set the TIME_ZONE to False in settings.py ( this will take away the timezone capability of your application) 2) or by comparing to timezone enabled datetime which the code as below: import datetime from django.utils.timezone import utc now = datetime.datetime.utcnow().replace(tzinfo=utc) Item.objects.filter(created = now) With this, the problem has been solved. More information c
Read more