Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Ran into another Firefox 3.0 bug with the cross-domain proxy. #61

Open
wants to merge 1 commit into
from

Conversation

Projects
None yet
2 participants

FX 3.0 spits out an error if link.styleSheet is undefined. Checking if undefined and then setting to empty object before rawCssText gets set.

@jaydiablo jaydiablo Ran into another Firefox 3.0 bug with the cross-domain proxy. FX 3.0 …
…spits out an error if link.styleSheet is undefined. Checking if undefined and then setting to empty object before rawCssText gets set.
b4a8154
Collaborator

doctyper commented Sep 27, 2011

Sorry, I'm a little confused. Are you trying to use the proxy with FF3, or is FF3 choking on this code regardless?

I believe it only happens when using the proxy (since that JS file shouldn't be loaded unless using the proxy). Not able to test that in the particular use-case I had, as the proxy was needed for respond.js to work at all (since we were doing cross-domain css files).

Collaborator

doctyper commented Nov 7, 2011

Two options here:

  1. Go this route, patch FF3 bug.
  2. Take care of this and further incompatibilities by wrapping respond.js in an IE conditional.

@scottjehl, @paulirish, any reason not to use a conditional?

If you wrap respond.js in a conditional, won't that keep it from being used for other browsers that don't support media queries that aren't IE (like firefox 3.0 and below, for example)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment