There’s isn’t any autoplay mode, but instead more like a regular PowerPoint slideshow. If you only want to have a slideshow of images, maybe JaS is a better alternative for you.

Thanks!
M

Well, the example above is very simple but in most, of not every, scenario you will have a lot of script in the page. To me a function call is still interaction, no matter how small. If it only had been one link, then you would naturally use getElementById instead.

In the end, to me it’s about doing things properly all the time. If one gets used to bad practices, they just tend to stick around for too long…

And thanks for liking the example!

By the way, I loved your example pleaseTeachMeProperJavaScript()!

Second it’s just a few bytes to download – for example, you don’t take processing power for the JavaScript loop into account either. Both is just neglectable.

I can understand your third reason, but again it’s just a function call. And it’s very simple (as opposed to DOM tree walking) and generic, so I can’t see much reason for change either. For anything more complicated I would use server-side includes to ease maintenance. After all, if you would really use this to show/hide layers, their location and maintenance (not to mention accessibility) would require a good concept anyway.

To begin with, the whole point is to separate content (HTML) from interaction (JavaScript); they should never be mixed together.

Second, with inline event handlers, they have to be downloaded by the web browsers all the time, as opposed to a JavaScript file that gets cached after it has been retrieved the first time.

Third, it’s about maintenance. If you have several web pages with different interaction you want one central place to control it, as opposed to having to go into each element in evey page to adjust things.

<a href="my-details.php" onclick=”showInfoLayer(); return false;”> My details</a>

It won’t mess with the link either when JavaScript is turned off. Or do I miss some important argument?

I’m happy to abide!

Thank you!

Yes, event handling sounds like a good idea for a part 2, but I wanted to keep this as simple as possible.

I guess that’s good advice too for anyone that already knows this stuff. Make it your mission to help a fellow developer use javascript properly if they don’t already know.

I think maybe you could have mentioned the use of an addevent function as in the real world it’s going to be common that you need to make use of more than one onload event. Alternatively an easily digestible explanation of the purpose of addevent functions could be part 2.