Perevodik.net

The address element has been around since the HTML3 spec was drafted in 1995, and it continues to survive in the latest drafts of HTML5. But nearly fifteen years after its creation, it’s still causing confusion among developers. So how should we be using address in our documents?

Until very recently the ability to play any type of audio within a browser involved using Adobe Flash or other browser plugins. Although Adobe’s Flash player is without doubt the most ubiquitous of these, most developers and designers would agree it is better not to rely on a plugin at all.

One of the most powerful interaction design patterns available to developers is “Drag and Drop.” We utilize Drag and Drop without really giving it much thought – especially when its done right. Here are 5 easy steps to ensure an elegant implementation.

I felt like playing around with things to see what could be done but accomplish it with a simpler HTML structure (no need for adding superfluous tags) and simpler code, too.
Changing the position of the background image felt to be the best approach to creating the type of effect we're looking for (and I'm not the first to think so: see the examples at the end of this article). jQuery is a great library for this type of task...

Paid links are something that use to be common practice for most SEO’s and agencies – simply spend, spend, spend and thou shall receive. This all changed when Google stated that manipulating search rankings from paid links should be avoided at all costs and if advertising is carried out then the appropriate “rel=nofollow” tag should be implemented to stop the flow of Page Rank.
While many SEOs headed back to the drawing board to think up new and innovating ways to attract links to websites some SEOs have continued to play the paid links game. I’m not one to judge, if you buy links, there are risks, if the pros out way the cons then go for it. There are plenty of large brands out there who have more than obvious paid links strategy, yet never seem to receive any penalties, in fact they seem to get rewarded by great rankings.

Web development is, in many cases, a process where time is a crucial factor. As coding is usually the last step in the process, all things come together and prior mistakes are revealed.
"Build this so it looks the same in all browsers, works better than the IA was ever planned and can fly." Or so we hear.
With a limited amount of time, developers are often tempted to fall for quick fixes and, not only due to last-minute changes, find themselves in a huge ball of code at the end of the project.
"What does that matter, if the site is working nicely, nobody complains and it's nodded off by the client?" I hear you ask.
This attitude is something I've encountered many times, and it usually results in a second-phase disaster, be it an extension of the site, a new face or a server change.

Simply, a custom event is something that happens that you feel is important enough to define actions to execute when this something happens. Clear as mud? I think I confused even myself. A custom event is just like a native event (onclick, onload, etc) except you define what it is and when it should fire.
Some explanation and implementation use the Yahoo User Interface library (YUI). I don’t use YUI. So I wrote up a simple class that allows you to implement custom events that is library independent.