Can anyone out there get the Respond polyfill asset work? I've tried, it never happens. Library downloaded, CSS aggregation enabled, caches triple flushed - never works for me: IE8 just loads up what looks like a no-media-queries version every time.

What's the secret? Any tips?

Comments

fubhy’s picture

fubhy CreditAttribution: fubhy commented
Status: Active » Fixed

If the layout has a no-query fallback it won't work because IE simply won't get any media queries. And there is no point in that anyways. If there is a no-query fallback, fine, no respond.js needed (and should not be needed/used, no-query fallbacks are much better and make much more sense than the respond.js polyfill).

So, to summarize: respond.js will ONLY have an effect on layouts that actually serve media queries to IE. If you have an *.no-query.css for the layout (e.g. see divine layout / ohm-hero layout) it won't have an effect.

dddbbb’s picture

dddbbb CreditAttribution: dddbbb commented

Yeah, I worked that one out and agree that a no-query fallback is a better solution. But I can't even get it to work when I am serving media queries to IE. I've never seen it work - and this is over a number of projects and various versions of Omega 4.

Does it work for you? Is the reason that nobody's mentioned it before down to the fact that they're simply not using it (using no-query fallbacks or simply don't care)?

I don't really mind that much as I don't plan to use it. I'm more interested in whether we're shipping an asset that doesn't ever kick in.

dddbbb’s picture

dddbbb CreditAttribution: dddbbb commented

It is probably me being stupid, but just thought I'd check...

fubhy’s picture

fubhy CreditAttribution: fubhy commented
Status: Fixed » Active

Can you come on IRC so we can debug this together? I don't have a testing environment for IE8 (yes, I generally don't care about IE8, heh). It needs to work, otherwise it's pretty pointless to have it in the first place. And I think it's still required in Omega 4.x because some people simply don't bother getting into no-query fallbacks (although I 100% encourage to use it and will probably add a note about it on the polyfill description).

dddbbb’s picture

dddbbb CreditAttribution: dddbbb commented

Sure but it'll have to be later as I'm tied up now (son's bath time!)...

fubhy’s picture

fubhy CreditAttribution: fubhy commented

When would be a good time for you to come on IRC?

dddbbb’s picture

dddbbb CreditAttribution: dddbbb commented

I'll jump on this afternoon. I have meetings this morning so can't say a time just yet.

dddbbb’s picture

dddbbb CreditAttribution: dddbbb commented

Am on IRC now. Will hang around for the rest of the afternoon (UK time).

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna commented
Issue summary: View changes
Status: Active » Closed (works as designed)

Closing this due to its age. If the problem persists in the latest -dev release, feel free to reopen it.

dddbbb’s picture

dddbbb CreditAttribution: dddbbb commented

Keep it closed! This is ancient and the thought of me even wanting to use Respond.js now is both shudder-inducing / embarrassing :D

For anyone else out there stumbling across this, go check out no-query fallbacks as touched on in #1 onwards. That said, I wonder why Respond.js was ever really suggested by Omega 4 - likely a different discussion that I'm not attempting to trigger right here - pretend I never mentioned it.

https://github.com/at-import/breakpoint/wiki/No-Query-Fallbacks