I have some media queries that are working well in IE, FF, and Safari. But when I resize my Chrome browser window looking at a site, the media queries don't seem to be taking effect. I know that in previous versions of Chrome, there had been issues with Chrome not working well with media queries. Is the same bug still applying with the update V.34? Or is there an alternative fix for this?

I was hoping to find a tool similar to FF Responsive Web Design Tool (even though it's not foolproof) for Chrome, but haven't found an alternative.

Suggestions?

mawburn
—
2014-04-08T22:59:44Z —
#2

toad78 said:

I was hoping to find a tool similar to FF Responsive Web Design Tool (even though it's not foolproof) for Chrome, but haven't found an alternative.

Chrome works just fine in this respect—at least on Mac. It works best if you dock the inspector to the right:

toad78
—
2014-04-14T16:48:47Z —
#4

Thanks, guys, but I'm still not able to figure out how to get Chrome to respond to media queries and I'm still seeing the same issue only in Chrome. If I take the browser and size it down, I see the main menu wrapping.

ralphm
—
2014-04-14T22:28:27Z —
#5

That sounds like a problem with your code rather than with the browser.

Any way to pinpoint? I'd imagine I can start over again, but I would rather narrow down the problem.

PaulOB
—
2014-04-15T20:24:09Z —
#8

It looks like you fixed the problem by reducing the width of the nav items

You should never make a nav fit the width by using pixel widths in a percentage layout. That nav could be done using display:table and display:table-cell without the needs for any widths and it would scale full width nicely and without breaking.

toad78
—
2014-04-15T20:29:57Z —
#9

Paul_O_B said:

It looks like you fixed the problem by reducing the width of the nav items

You should never make a nav fit the width by using pixel widths in a percentage layout. That nav could be done using display:table and display:table-cell without the needs for any widths and it would scale full width nicely and without breaking.

Thanks, Paul O'B. I'll have to keep that in mind if I come across this type of issue again. Using display:table was the furthest from my mind.