On 14 May 2010 18:51, Jonathan Steel <[email protected]> wrote: >> Invalid pages in the browser are just as evil, aren't they ;-) I >> sometimes wish browsers were a lot less forgiving on that part, it >> would avoid a lot of seemingly unrelated issues, especially when you >> start using Javascript DOM manipulations. > > Yah I knew somebody would bring that up as soon as I made my last > comment. I think the problem is probably due to our DOM manipulation. > Our site renders properly in every browser we have tried, so it took me > really by surprise then these html parsers started choking on the pages.
It may render ok at the moment, but can you sleep soundly knowing you have invalid html and that the next release of firefox may interpret the invalid html in a different way? Colin -- 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.
