123
-=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- (c) WidthPadding Industries 1987 0|251|0 -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=-
Socoder -> Web Development -> Internet Explorer, I hate you!

Tue, 31 May 2011, 03:54
Afr0
Does anyone have any idea why this website doesn't display the image header in IE7?

Adding the strict doctype made the site display somewhat better, but the image still isn't displaying :|



-=-=-
Afr0 Games

Project Dollhouse on Github - Please fork!
Tue, 31 May 2011, 04:31
Jayenkai
> Reveal 🔎
Works fine in IE 9.0.8112.16421 64-bit edition
> Reveal 🔎

-=-=-
''Load, Next List!''
Tue, 31 May 2011, 04:51
JL235
It's not a version number, it's a build number. That is why it's so long, and with so many builds it needs to be.
Tue, 31 May 2011, 05:45
Afr0
Whoops, I meant IE 8...
IE8 is the latest browser we can support at work, as they haven't invested in Vista. :\
And my boss can only use IE8 on his PC because he claims that Google Chrome has issues interacting with some other programs he's installed, and I'd rather not force him to install another browser.

*sigh*

-=-=-
Afr0 Games

Project Dollhouse on Github - Please fork!
Tue, 31 May 2011, 06:43
JL235
Try adding IE-Edge. You can find that, and other goodies, over at HTML5 Boilerplate.
Tue, 31 May 2011, 12:36
Stealth
Internet Explorer broken? Welcome to web development.

-=-=-
Quit posting and try Google.
Tue, 31 May 2011, 12:50
9572AD
I seem to recall people using Netscape because IE3 (or 4?) was broken. Has any version of IE not been horribly broken?

-=-=-
All the raw, animal magnetism of a rutabaga.
Tue, 31 May 2011, 13:23
CodersRule
You put the <p> that contains the image in the head section, when it needs to be in the body. Move it down a few lines.
Tue, 31 May 2011, 13:48
Jayenkai
... Today's lesson comes from Star Trek : TNG.
While the older techy guys are squabbling, Wesley Crusher solves it...

-=-=-
''Load, Next List!''
Tue, 31 May 2011, 14:23
Afr0
You put the <p> that contains the image in the head section, when it needs to be in the body.


Huh? Why does it have to be in the body? It works fine in Google Chrome...

-=-=-
Afr0 Games

Project Dollhouse on Github - Please fork!
Tue, 31 May 2011, 14:42
9572AD
Unless something's changed, the HTML <head> is just for meta tags and doctypes and stuff; all visual content - page headers, footers, sidebars and what have you - go in the HTML <body>

-=-=-
All the raw, animal magnetism of a rutabaga.
Tue, 31 May 2011, 14:47
Dabz

Huh? Why does it have to be in the body? It works fine in Google Chrome...


I've found Chrome to be very un-nitpicky about stuff... I had a right chew with tables, things were going great in Chrome, but, as soon as I tested on IE and FF... It was downhill!

So, I fixed it up to work in IE, though and behold, it worked fine in FF and Chrome.. Go figure!?!

Dabz

-=-=-
Intel Core i5 6400 2.7GHz, NVIDIA GeForce GTX 1070 (8GB), 8Gig DDR4 RAM, 256GB SSD, 1TB HDD, Windows 10 64bit
Tue, 31 May 2011, 19:56
JL235
IE isn't actually broken though, it's been free of any major bugs since about IE 5 (or earlier). The issue is that it doesn't support anything; that's the problem!
Tue, 31 May 2011, 20:13
CodersRule
Chrome just renders it the best it can. If it doesn't know what to do, it makes its best guess.

<head>, like 9572AD said, is only for non-content stuff.
all of your actual content should be in the <body> tag.
Tue, 31 May 2011, 21:51
JL235
The new HTML5 spec actually allows you to close tags (or at least certain tags) in an incorrect order. However browsers have been dealing with this in one way or another for years.

@Afro: if your gonna use HTML4 then I'd recommend using XHTML instead. It'll catch all these bugs for you!
Wed, 01 Jun 2011, 00:44
Afr0
Pah, I moved the image class and the CSS link down, yet IE8 still refuses to display the image!
Diablos: I don't know XHTML!

-=-=-
Afr0 Games

Project Dollhouse on Github - Please fork!
Wed, 01 Jun 2011, 03:31
JL235
It's very similar to HTML, it's just properly formed. See the Wikipedia article for more info.

The main reason I suggest it is because the browser will refuse to display the page if it contains bugs, and instead will point out the bugs to you. This makes debugging XHTML documents much easier then HTML.
Wed, 01 Jun 2011, 07:12
HoboBen
On a page on its own (in the same directory).

Try:
<img src="Agdernering-silver.jpg" alt="" width="100" height="100" />
<img src="Agdernering-silver.jpg" alt="" width="100" height="100">
<img src="./Agdernering-silver.jpg" alt="" width="100" height="100">
<img src="./Agdernering-silver.jpg" alt="" width="100" height="100" />

With and without a doctype and <head><body> structure.

Do any of those work?

Does "Agdernering" mean "banner" or something? Could it be ad-blocked?

-=-=-
blog | work | code | more code
Wed, 01 Jun 2011, 07:25
JL235
Google for FireBug-lite and add it to your site. Then you have FireBug in IE.

Next you can inspect your page and find the image link, and then have a look to see if it's able to find the image. It could be that the image link is broken, or some other issue with how IE is parsing your HTML.
Mon, 06 Jun 2011, 01:43
Afr0
On a page on its own (in the same directory).

Try:
<img src="Agdernering-silver.jpg" alt="" width="100" height="100" />
<img src="Agdernering-silver.jpg" alt="" width="100" height="100">
<img src="./Agdernering-silver.jpg" alt="" width="100" height="100">
<img src="./Agdernering-silver.jpg" alt="" width="100" height="100" />

With and without a doctype and <head><body> structure.

Do any of those work?

Does "Agdernering" mean "banner" or something? Could it be ad-blocked?


I tried, with and without a doctype and header and body. It doesn't work. None of the images will display!
'Agdernering' doesn't mean banner, no.

Diablos: I added Firebug, but I don't see the point..?
As far as I can see, IE parses the links correctly (Firebug shows the same sourcecode as IE does)

-=-=-
Afr0 Games

Project Dollhouse on Github - Please fork!
Mon, 06 Jun 2011, 02:11
JL235
FireBug isn't about viewing source, it's about being able to look at elements easier and to make it easier to follow image links to see if they are valid or not.

Anywho, try using the explicit path to the image (i.e. /images/Agdernering). You should do this anyway as relative paths will break the moment the page is moved.
Mon, 06 Jun 2011, 02:58
Afr0
Phew, I finally got it to work. I had to explicitly use the full address;



As well as convert it to a PNG (IE doesn't like JPG)

-=-=-
Afr0 Games

Project Dollhouse on Github - Please fork!
Mon, 06 Jun 2011, 03:08
JL235
I wouldn't include the http bit of the address, just use '/agdernering/Agdernering-silver.PNG'.

Using the whole domain is bad because it means if you ever change domain (including working locally or setting up a dev server) then it will break.