Again, this is just a bug in Safari's rendering engine... :) Prototype doesn't "break" Safari, it's broken to start with... ;) I'd go with the pragmatic fix and telling safari to give a background to the HTML element, too.
Btw, solves some rendering bugs in Firefox too, that can happen under specific circumstances. OMG, BROWSERS!!! ;) As for the XHTML 1.0 strict issue -- I recommend using XHTML 1.0 Transitional as the "most compatible" doctype; and serving it as text/ html. These days, that seems to be the way to go: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd "> Best, Thomas Am 27.11.2007 um 13:49 schrieb RobG: > > > > On Nov 26, 7:42 pm, ftx <[EMAIL PROTECTED]> wrote: >> Hi there! >> >> I have the following problem and don't know how to come by this. If I >> include prototype.js and scriptaculous.js Safari gets a problem with >> coloring the background of the viewport. It only works where you >> placed some div, the rest of the page won't be correctly colored at >> first. If you resize the window everything is fine. > > I think what you are seeing is a conflict between HTML and XHTML. You > pretend that your page is XHTML 1.0 Strict, but it is in fact served > as text/html. It is also invalid XHTML - you are missing the closing > shortag on the meta element. > > If you correct the error and serve your page as XHTML, you will get > the same result in Firefox and Safari - even if you remove all scripts > from the file (but of course you will get nothing in IE, which has no > idea what XHTML is). > > As to why there is a difference between XHTML and HTML, I suggest you > ask in > > news:comp.infosystems.www.authoring.html > <URL: > http://groups.google.com.au/group/comp.infosystems.www.authoring.html?hl=en&lnk=li >> > > Be prepared to weather some flak for using XHTML at all, but I think > you will get the answer. > > Further, scriptaculous.js loads all the other files, so there is no > need to include them all - you are just creating twice the number of > script elements as are required. > > And lastly, the effect you see with HTML and Safari (i.e. if you serve > a valid HTML document as HTML rather than invalid XHTML) occurs if you > include any script file after prototpye.js - it doesn't seem to matter > what it is, or even if it exists. > > I don't have time to track it down any further than that, but I > suggest you start by looking at the functions that run when > Prototype.js is loaded. > > > -- > Rob > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" 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-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
