ansaurus

Question

Voodoo magic interfering with my javascript, I am going crazy.

Answer 1

A:

I see the problems you describe. FireBug also shows installation.html is messed up. Try copying a working HTML file (e.g. customercare.html) atop installation.html and see what happens.

Upper Stage 2010-01-14 18:09:53

If Guffa is correct, copy customercare.html atop installation.html, edit installation.html, and cut-and-paste old contents into new file. I think that will fix your problem.

Upper Stage 2010-01-14 18:13:27

see the above answer about file encodings, we're getting somewhere.

Sneakyness 2010-01-14 18:14:26

Yes - it looks good to me now.

Upper Stage 2010-01-14 18:18:52

Answer 2

+6 A:

You have saved the file as UTF-16, so it loads the css files and scripts as UTF-16 also. Save the file as UTF-8 instead.

Guffa 2010-01-14 18:10:30

That's what I'd say too, but the odd thing is that it sometimes comes up broken, and sometimes not, when you press reload repeatedly. Also, when I force UTF-16 in Firefox, it still comes up as gibberish. Still, that's the most probable reason.

Pekka 2010-01-14 18:11:33

Sneakyness, you should be able to choose an encoding in your editor.

Pekka 2010-01-14 18:12:46

Coda has a selector for it, I changed it to UTF-8, now it's entirely in chinese!?!?!

Sneakyness 2010-01-14 18:13:55

Works for me now (FF 3.5 on Windows 7).

Pekka 2010-01-14 18:14:28

Never seen this before, lol!It's Chinese on FF 3.5.6 on Windows XP

Harmen 2010-01-14 18:15:51

Works for me now.

Upper Stage 2010-01-14 18:16:15

Works for me as well. Thanks! You're a champ.

Sneakyness 2010-01-14 18:16:17

Good find - this is definitely it. A `<meta/>` for the content-type w/a charset wouldn't hurt, either.

Peter Bailey 2010-01-14 18:18:27

+1 to Peter Bailey! That meta is `<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">`

artlung 2010-01-14 19:02:40

Answer 3

A:

Hi Sneakyness,

Your page doesn't validate, maybe that's it.

First of all, add a doctype to your HTML-code and some more content-encoding stuff:

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"&gt;
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
    <meta http-equiv="content-type" content="application/xhtml+xml;charset=utf-8" />
    <meta http-equiv="content-style-type" content="text/css" />
    <link
    (...)

Harmen 2010-01-14 18:12:10

no. Everything validated before I tore everything apart to figure out this bug.

Sneakyness 2010-01-14 18:14:58

The validator says that you need to add character encoding, which seems to be the problem...

Harmen 2010-01-14 18:17:41

regardless of what the contents of the file says it's encoded in, if I encode the file as something else, those have no effect.

Sneakyness 2010-01-14 18:19:19

A doctype and a content-type is a good idea, even if it's not the solution to this exact problem. No xml tag before the doctype though, or IE will ignore the doctype. What to use for content-type is up for debate, but that doesn't matter that much, it's the charset part that is most useful.

Guffa 2010-01-14 18:23:27

ansaurus

tags:

views:

answers:

Voodoo magic interfering with my javascript, I am going crazy.

related questions