Meliza,
This is not a PGV bug, simply the different ways that the browsers show an image that it can't retrieve. There is no simple way for the app to deal with this, and even if there was, it is not something that we should do.
Save the following line as missingImage.html and open it in both IE and FireFox to test this.
<img src="something.jpg" alt="title of missing media" />
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If I am not mistaken, it was agreed that we would show an icon for external URL media in a similar way to what we show for documents, jpg, gif etc. files.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If I am not mistaken, it was agreed that we would show an icon for external URL media in a similar way to what we show for documents, jpg, gif etc. files.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have been thinking about this, but it isn't as trivial as it sounds. The current implementation assumes the url points directly at a remote media object, which is fairly reasonable. The broken images only occur when you link to an html file instead of a media file.
I'd be pretty happy for any off-site link to be a generic one. If the user cared, then they could inspect the URL before they click it. But there's so many variations of what the link might be ... page.cgi , page.pl , page.htm , page.html , page.shtml , page.php , page.stm , page.py and so on and so on and so on.
What do others think?
Mark
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=634811
Originator: NO
Meliza,
This is not a PGV bug, simply the different ways that the browsers show an image that it can't retrieve. There is no simple way for the app to deal with this, and even if there was, it is not something that we should do.
Save the following line as missingImage.html and open it in both IE and FireFox to test this.
<img src="something.jpg" alt="title of missing media" />
Logged In: YES
user_id=959928
Originator: YES
If I am not mistaken, it was agreed that we would show an icon for external URL media in a similar way to what we show for documents, jpg, gif etc. files.
Logged In: YES
user_id=959928
Originator: YES
If I am not mistaken, it was agreed that we would show an icon for external URL media in a similar way to what we show for documents, jpg, gif etc. files.
Logged In: YES
user_id=45016
Originator: NO
Ah, well that's not the bug you reported :)
I have been thinking about this, but it isn't as trivial as it sounds. The current implementation assumes the url points directly at a remote media object, which is fairly reasonable. The broken images only occur when you link to an html file instead of a media file.
In terms of the ideal state, what would you like to see if you linked to each of these files:
http://www.server.com/path/file.jpg
http://www.server.com/path/file.pdf
http://www.server.com/path/file.html
http://www.server.com/path/file.php
I don't think a standard "url" icon on each of those would be too helpful.
Logged In: YES
user_id=623181
Originator: NO
See my "bug" #1818279 where there is an attempt to link to URL.jpg ... by Lightbox ... except that it doesn't exist either.
A standard URL icon would do for me ... I might also link to a .asp page or even just a directory eg
http://www.server.com/path
It used to be done in PGV 3.x
Mark
Logged In: YES
user_id=45016
Originator: NO
But that's what I'm getting at, for this url:
http://www.server.com/path/file.pdf
wouldn't you rather see a pdf icon rather than a "url" icon?
And for this:
http://www.server.com/path/file.jpg
wouldn't you rather see a small version of the actual image?
Why should we show a generic url icon just because the link is offsite?
Logged In: YES
user_id=623181
Originator: NO
I'd be pretty happy for any off-site link to be a generic one. If the user cared, then they could inspect the URL before they click it. But there's so many variations of what the link might be ... page.cgi , page.pl , page.htm , page.html , page.shtml , page.php , page.stm , page.py and so on and so on and so on.
What do others think?
Mark