jeffman

var option1 = document.createElement("option");option1.text = "1";option1.value = "1"; var option2 = document.createElement("option");option2.text = "2";option2.value = "2"; btn.appendChild(option1);btn.appendChild(option2); // and so on It would be neater if you used a loop. It would be even neater if you clone the entire select element. Note that appendChild probably works in all/most browsers with option elements, but the recommended way is to use the add() method of the select element. That is a little tricky, since old versions of IE require special treatment. It might be useful to try appendChild in every browser you have access to.

I misunderstood. I thought you were already creating elements. This might be a lot to learn. You should start by giving the important elements id attributes, like your form. createElement and appendChild will be important methods to use. The examples may help. cloneNode might be an alternative that could simplify some tasks. You could wrap your form elements in a fieldset element, and then just clone the whole fieldset at once. You would still need to update the names of the elements.

You need to post the code you're using now so we can show you what to change.

Another problem. I suspect you are testing in FF or IE. Neither of those has implemented the type="date" input. So it acts like a plain text input. Try your code in Chrome. You will find that Chrome expects to receive the date value in a very specific format. Unfortunately, I'm too lazy to read if the Chrome format is or will become an industry standard. I can say that the output of a.setFullYear(0,0,0) is NOT the expected format.

HTML and CSS don't do very much. Testing is behavior. Things need to happen. That means programming or adapting someone else's program to your page. I don't know what to add to that, unless you want more clarification on the difference.

callumacrae, I think everyone welcomes a seasoned developer on the board. But there are some matters you may wish to hold back on until you've absorbed more of the spirit of the board, who we are, and what the members are looking for.

Validators are machines, so they don't always understand the source of an error. You don't actually have an attribute error. Something else is wrong that makes the validator think there is an attribute problem. As thescientist said, please pay attention to the way I am trying to help you.

LOL. Anyone who knows what unit testing is probably doesn't need to ask about it. I think ndbbb wants to be able to give a test the way a teacher tests a student. If I'm right, you'll need to learn some programming skills. If you don't want test-takers to cheat, the programming will mostly happen on your server using a language like PHP. If you've never done this before, you have a lot to learn just to get started. Have you looked into a simple courseware package that already exists? This Google search might help.

I'm pretty sure the error is on this line. <img id="rot" src="http://www.linkedin.com/img/webpromo/btn_viewmy_120x33_es_ES.png?locale=" width="120" height="33" border="0" alt="Ver el perfil de Eduard Lid en LinkedIn"</image>* Remember what kind of tag this is and the correct way to close it. Remember there is no <image> tag.

Sorry, I tried to delete that as quickly as I could. The page you link to is filled with ads, and I didn't see your download at first.

.

It is not automatically bad practice, and good developers do it frequently. That said, it's possible to make a mess out of anything. From a strictly CSS point of view, this technique is useful if multiple elements need the same style (create a class) and a single member of that class needs to modify 1-2 aspects of that style (use the ID).

Since I suggested your container be 1000px wide, I now suggest it be 960px wide, to match your slideshow. I also suggest you not have so much padding-left on your links.

When I looked before, site50 looked the same. It's better now, but I think you should center #container.

Is what OK?

No. The kind of container I mean contains everything. An outline of your page would be this: <!DOCTYPE html><html> <head> <!-- stuff --> </head> <body> <div id="container"> <!-- stuff --> <!-- stuff --> <!-- stuff --> </div </body></html>

Fieldset lets you have that nifty legend element. It's also more semantic than a plain div. A lot of developers don't care about semantics; I do, and W3C encourages it.

My display at work is 1680px wide. The design does not look good. The elements on the left and right sides are too far away from the content area. If you cannot fill most of the screen, try using a container div in the center that is around 1000px wide. Put everything in that.

CSV will transmit just like text, and then JavaScript can break break it up very easily. Also, it's less bandwidth crazy than XML. But yeah, 5000 lines . . .

I wrote this in Post #42. You already know how to give an element a classname. Do it for these links too. You don't need to add a span. A class can usually be applied to any element.

There are no important errors now. Start a new thread and explain the next thing you want to do.

OK, you fixed that. Now give your other links a class name.

We know what your code looks like. We have all visited your page many times. The problem is in the line I showed you. Try this. Click your slideshow. Notice that it is a link to your portfolio page. Ask yourself why this should be. Then look again at the line I showed you. Remember I said that something is missing.

He took it down and replaced it with his old code. That's why we're fixing the old code AGAIN.

You should notice something wrong with this line that affects everything that follows. Something MISSING. <span class="style3" lang="en-gb"><a href="portfolio.html">Portfolio</span> Again, if you checked the validator, you would see the answer in the first two errors.