I’ve got a page that has been up for most of a year but in Yosemite it shows up as a totally blank page with both Safari and Firefox. It displays just fine in both browsers in Mountain Lion. The page has an HTML5 animation that plays a few second of audio at the start. The audio plays so I know the content is there somewhere. I’m not sure why this would kill all the page content.
Other pages on the site with HTML5 content work just fine.
As this identical problem occurs in both browsers, I assume that Apple has diddled with how web pages display.
Is there some workaround? This is a corporate site, which makes this urgent.
The newer versions of Safari may be less forgiving of malformed code - that is to say, code that was added as markup and written incorrectly. You have a container of divs before the PageDiv element in which the first contained div doesn’t have a closing tag. The container itself has a style of display:none and the Webkit browsers-- trying to understand your structure-- have put the closing tag at the end of the PageDiv element, thus conferring the display:none style to the entire page contents. Add the missing closing tag and the page is visible again.
<div style="display:none">
<div>What do you want in a shutter? <!-- missing </div> goes here -->
<div>rock-solid reliability</div>
<div>transferable warranty</div>
<div>genuine american hardwood</div>
<div>enduring beauty</div>
<div>shutters</div>
<div>separated, rotated & bonded like a fine musical instrument</div>
<div>bookmatched hardwood</div>
<div>adding strength & stability</div>
<div>milled from the louver itself</div>
<div>slimmer louver</div>
<div>monolithic tenon</div>
<div>no plastic pins</div>
<div>no drilling</div>
<div>stronger design</div>
<div>mortise &tenon joinery</div>
<div>screw reinforced</div>
<div>tilt rod with continuous metal insert</div>
<div>thousands of variations</div>
<div>impeccable deep luster finishes</div>
<div>widest range of mounting options</div>
</div>
Also… you went out of the way to make an html5 animation but your page did is html 4.01 Transitional… why not make it html5?