Msg#: 4089217 posted 12:55 pm on Mar 1, 2010 (gmt 0)
Hello, I'm very new to writing html and I have made web pages for my phd project (marine biology..). They seem to work fine in IE when I test them offline, but photos, links and graphics don't seem to work in FF. They are there and I can right click and choose to display them in a new tab but they don't appear automatically. Don't know if it's my code or some safety settings on the browser! I'm only using html, no external style sheet.
Msg#: 4089217 posted 3:56 pm on Mar 1, 2010 (gmt 0)
Thank you for any tips.
With off line I mean that I'm just testing it on my computer. In IE or in FF I just write the F:\webpage etc and see what it looks like. (It's not yet on a server). And the page looks fine in IE but in FF the pictures don't show. BUT, table and the frame for the picture shows and it has a small symbol of torn paper? (I think) in the frame. I can right click inside the frame and open the picture in a new tab so the browser has to read the script, right?
Msg#: 4089217 posted 6:40 pm on Mar 1, 2010 (gmt 0)
Well, I am making the assumption you are using Windows due to the backslashes. For a full path URL, FireFox needs something like "file://F\:webpage\logo2.jpg" - but don't use that, it may be specifically incorrect and you'd have to change it anyway when you upload to a server.
If this page is in the "webpage" directory, link to your images and other links relative to this page - like
Another example, let's say you organize this so you have
With images being a folder/directory.
When you upload to a server, I'd replace it with this:
Because being on a web server, this always means to start at the domain root, which allows you to create directory structures without having to use relative "toothpick syntax." Note that offline this will not work because your computer is not a web server. You'd need to remove the first slash viewing locally, replace it when deployed to the server.
Note also the forward slashes now; browsers will resolve them locally just fine, but it's that "where do we start?" at the beginning of the src/href that is causing the local problems.
I would follow both of the above concepts in your links, too: