Colin Law wrote in post #1015781: > The first thing to do is to get to valid html. You cannot make any > conclusions about anything with invalid html. To check that it is > valid view the page source (View > Page Source or similar in your > browser) copy the complete text and paste it into the w3c html > validator. When you have invalid html the browser (which will know > that it is invalid) has to guess what you meant and it may not guess > the way you intended. > > There is no point doing anything else until you have valid html. A > golden rule of problem solving, if you know that something is not > right then fix it before worrying about other things that may or may > not be part of the problem. > > Colin
Thanks for this information, i didn't know that w3s have a validator for html, now i can use it to check things faster that using firebug or other things. It seems like the site have a lot of things wrong, like i spected for what i saw the first time in the source code, but the thing here is that i don't own that site so i can't do something about that issues. -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
