The application I'm building requires my user to set 4 pieces of information before this image even has a chance of loading. This image is the center-piece of the application, so the broken image link makes it look like the whole thing is borked. I'd like to have another image take its place on a 404.
Any ideas? I'd like to avoid writing a custom directive for this.
I was surprised that I couldn't find a similar question, especially when the first question in the docs is the same one!
I suggest that you might like to use the Angular UI Utils 'if statement' directive to solve your problem, as found at http://angular-ui.github.io/. I have just used it to do exactly the same thing.
This is untested, but you could do something like:
Controller code:
(or simpler)
HTML in View:
<img ui-if="showImage()" ng-src="images/{{data.value}}.jpg" />
Or even simpler, you could just use a scope property:
Controller code:
HTML in View:
<img ui-if="showImage" ng-src="images/{{data.value}}.jpg" />
For a placeholder image, just add another similar
<img>
tag but prepend yourui-if
parameter with an exclamation (!
) mark, and either make ngSrc have the path to the placeholder image, or just use asrc
tag as per normal ol' HTML.eg.
<img ui-if="!showImage" src="images/placeholder.jpg" />
Obviously, all of the above code samples are assuming that each of value1, value2, value3 and value4 will equate to
null
/false
when each of your 4 pieces of information are incomplete (and thus also to a boolean value oftrue
when they are complete).PS. The AngularUI project has recently been broken in to sub-projects, and the documentation for
ui-if
seems to be missing currently (it's probably in the package somewhere though). However, it is pretty straightforward to use as you can see, and I have logged a Github 'issue' on the Angular UI project to point it out to the team too.UPDATE: 'ui-if' is missing from the AngularUI project because it's been integrated in to the core AngularJS code! Only as of v1.1.x though, which is currently marked as 'unstable'.
Little late to the party, though I came up with a solution to more or less the same issue in a system I'm building.
My idea was, though, to handle EVERY image
img
tag globally.I didn't want to have to pepper my
HTML
with unnecessary directives, such as theerr-src
ones shown here. Quite often, especially with dynamic images, you won't know if it's missing until its too late. Adding extra directives on the off-chance an image is missing seems overkill to me.Instead, I extend the existing
img
tag - which, really, is what Angular directives are all about.So - this is what I came up with.
Note: This requires the full JQuery library to be present and not just the JQlite Angular ships with because we're using
.error()
You can see it in action at this Plunker
The directive looks pretty much like this:
When an error occurs (which will be because the image doesn't exist or is unreachable etc) we capture and react. You can attempt to get the image sizes too - if they were present on the image/style in the first place. If not, then set yourself a default.
This example is using placehold.it for an image to show instead.
Now EVERY image, regardless of using
src
orng-src
has itself covered in case nothing loads up...If image is 404 or image is null empty whatever there is no need for directives you can simply use ng-src filter like this :)
Here's a solution I came up with using native javascript. I'm checking if the image is broken then adding a class to the image just in case and changing the source.
I got part of my answer from a Quora answer http://www.quora.com/How-do-I-use-JavaScript-to-find-if-an-image-is-broken
Is there a specific reason you can't declare the fallback image in your code?
As I understand, you have two possible cases for your image source:
I think this should be handled by your app - if the correct URL cannot currently be determined, instead pass a loading/fallback/placeholder image URL.
The reasoning is that you never have a 'missing' image, because you have explicitly declared the correct URL to display at any point in time.
This will allow only to loop twice, to check if the ng-src doesn't exist else use the err-src, this prevents the continues looping.