perryb

OK fess up time – Firebug Lite is the culprit. I really should have checked the plug ins. I had a blinding flash of inspiration – its only taken me three months to work it out :S

So, to recap: Firebug Lite is the cause of blank screens between page loads in Google Chrome.

Actually – and I feel a little bit daft now – it seems that this a quirk of Google Chrome. I went off and tried a few CMS based sites including the BBC and many do the same thing, the window briefly goes blank whilst teh next page loads.

TBH this is a bit clunky on Chrome’s part, none of the other browsers do this, though in the case of the WordPress site that I’m testing it seems that Chrome loads much faster than the competiton so its swings and roundabouts really.

No I didn’t get any response on the Thematic forum either (though that’s not to say it is a Thematic specific problem).

Here is a site that I’m working on currently – I’ve got it running on Nginx with WP Super Cache.

The thing is the site loads fast enough in Chrome but the screen still goes blank between page loads. I think it must be a Chrome issue.

Has anyone noticed the same behaviour in Google Chrome with child themes (I suppose I should try this out myself when I get time)?

It looks as though you got it working OK (“the one that does not” link has fully functioning mega drop downs).

Could you share how you managed to get it working in the end? The drop downs look really good and very nicely laid out too.

Perry

One last bump before bed time.

To recap: Google Chrome appears to suck when child themes are installed on WordPress.

I’d still be interested in hearing if anyone has experienced the same problem.

Good work on this explanation mfields. Much appreciated!

This is just too stupid – make sure you call name your file in your child theme “functions.php” not “function.php”!!

Doh – thanks for dropping by demetris!

That’s odd!

I pasted it into a blank functions.php in a child theme folder with <?php … ?> wrapped round it and it didn’t even register.

I wonder what I’ve missed?

OK I seem to have found the solution.

At line 74 in the Twenty Ten header.php there is the following line of code:

$image[1] >= HEADER_IMAGE_WIDTH ) :
// Houston, we have a new header image!

And in functions.php there is the following:

// The height and width of your custom header. You can hook into the theme's own filters to change these values.
	// Add a filter to twentyten_header_image_width and twentyten_header_image_height to change these values.
	define( 'HEADER_IMAGE_WIDTH', apply_filters( 'twentyten_header_image_width', 940 ) );
	define( 'HEADER_IMAGE_HEIGHT', apply_filters( 'twentyten_header_image_height', 198 ) );

	// We'll be using post thumbnails for custom header images on posts and pages.
	// We want them to be 940 pixels wide by 198 pixels tall.
	// Larger images will be auto-cropped to fit, smaller ones will be ignored. See header.php.
	set_post_thumbnail_size( HEADER_IMAGE_WIDTH, HEADER_IMAGE_HEIGHT, true );

Twenty Ten tests to see if your image is larger than or equal to the default width of 940px – if it is it becomes the custom header image. These values can be customised with filters.

Perry

Hi it happened to me too – running Firefox 3 and WordPress (Turbo switched on) on a local install (using Xampp) on an XP netbook.

Disabling Gears in Firefox as per the instructions above was all was needed to get back on track again.