image scrolling
-
using java scipt how to scroll images
-
using java scipt how to scroll images
You're going to have to go into a LOT more detail than that.
Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles. Dave Kreskowiak
-
using java scipt how to scroll images
Simplest example:
And now for a better question: Why can't I point to a file that is not in the same folder as the HTML file referencing the image I want to display? [EDIT] ... by hardcoding it in the body as a string, that is, like here, but providing a full path and drive location ..? [/EDIT]
-
Simplest example:
And now for a better question: Why can't I point to a file that is not in the same folder as the HTML file referencing the image I want to display? [EDIT] ... by hardcoding it in the body as a string, that is, like here, but providing a full path and drive location ..? [/EDIT]
RedDk wrote:
a full path and drive location
If you're loading an HTML file from your local disk, then you should be able to reference images from the same disk using a file path. (Although a File URI[^] would probably be safer.) If you're loading HTML from a website, then you cannot reference files on "your" local disk by providing a path and drive location. That path would refer to a location on the end-user's computer, which may not exist, or probably wouldn't contain the expected image. But even if it did, allowing websites to read the contents of their users' local file system would be a security risk.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
RedDk wrote:
a full path and drive location
If you're loading an HTML file from your local disk, then you should be able to reference images from the same disk using a file path. (Although a File URI[^] would probably be safer.) If you're loading HTML from a website, then you cannot reference files on "your" local disk by providing a path and drive location. That path would refer to a location on the end-user's computer, which may not exist, or probably wouldn't contain the expected image. But even if it did, allowing websites to read the contents of their users' local file system would be a security risk.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Lets see, how shall I word this ... It sounds as if I do indeed have a problem loading an image using an HTML file that I saved to my hardrive when, in fact, what I meant to say is that I would obviously use a script. And to show where the file is so that a function could get it for me I'd use "imageURL" and "push" it. But being in a rhetorical holiday mood I was being facetious and using this fast-as-all-get-out < img src= /> tag in order to make my sarcastic point. Why answer? Because using < img src="file:///C:/Users/Member_13108495/images/pianoGrande.jpg" /> loads only a broken page icon WHEN the HTML is using an extant path. The real point is that, in my understanding of it ... for purely security reasons, as you state, shuffling through the contents of a hardrive using a webbrowser is faux pas (even though Firefox doesn't "seem to have any problems with that" (quoting some nerd on SO yesterday)). The only way one could use < img src= /> is what I said in the displayed example I provided; the image has to be in the folder where the .html resides.
-
Lets see, how shall I word this ... It sounds as if I do indeed have a problem loading an image using an HTML file that I saved to my hardrive when, in fact, what I meant to say is that I would obviously use a script. And to show where the file is so that a function could get it for me I'd use "imageURL" and "push" it. But being in a rhetorical holiday mood I was being facetious and using this fast-as-all-get-out < img src= /> tag in order to make my sarcastic point. Why answer? Because using < img src="file:///C:/Users/Member_13108495/images/pianoGrande.jpg" /> loads only a broken page icon WHEN the HTML is using an extant path. The real point is that, in my understanding of it ... for purely security reasons, as you state, shuffling through the contents of a hardrive using a webbrowser is faux pas (even though Firefox doesn't "seem to have any problems with that" (quoting some nerd on SO yesterday)). The only way one could use < img src= /> is what I said in the displayed example I provided; the image has to be in the folder where the .html resides.
@RedDk said in image scrolling:
Lets see, how shall I word this ... It sounds as if I do indeed have a problem loading an image using an HTML file that I saved to my hardrive when, in fact, what I meant to say is that I would obviously use a script. And to show where the file is so that a function could get it for me I'd use "imageURL" and "push" it. But being in a rhetorical holiday mood I was being facetious and using this fast-as-all-get-out < img src= /> tag in order to make my sarcastic point. Why answer? Because using < img src="file:///C:/Users/Member_13108495/images/pianoGrande.jpg" /> loads only a broken page icon WHEN the HTML is using an extant path. The real point is that, in my understanding of it ... for purely security reasons, as you state, shuffling through the contents of a hardrive using a webbrowser is faux pas (even though Firefox doesn't "seem to have any problems with that" (quoting some nerd on SO yesterday)). The only way one could use < img src= /> is what I said in the displayed example I provided; the image has to be in the folder where the .html resides.
Got it, thanks for explaining. Yes, browsers usually block local file access for security, so keeping the image in the same folder as the HTML file is the simplest way to make it load. -
javascript does not support client-side file systems. The fact that you can do it locally means tyour system is the "server", and hat's why you can access it. If you want the user to be able to scroll a file when the site is actually deployed on a real web serer, you have to load the file from a suitable url. this means that the file must be somewhere on the internet (note "the internet" does NOT include a user's local file system).
