Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Firefox on Mac OSX #2

Closed
wesamly opened this issue Jan 1, 2013 · 10 comments
Closed

Firefox on Mac OSX #2

wesamly opened this issue Jan 1, 2013 · 10 comments

Comments

@wesamly
Copy link

wesamly commented Jan 1, 2013

Hi,
The included example produces the following error on Firefox 17.0.1 / Mac OS X 10.8.2:
WebKitCSSMatrix is not defined

Only gets empty page with the pattern background.

good luck.

@jeffgca
Copy link

jeffgca commented Jan 14, 2013

Seems like this could be used as a polyfill: https://gist.github.com/394537

@koenbok
Copy link
Owner

koenbok commented Feb 13, 2013

This should be doable, but it's not really important to me because Framer is intended as a prototyping tool for Webkit. So I'm going to focus on other things but pull requests are always welcome.

@imikay
Copy link

imikay commented Feb 18, 2013

I think you should at least to tell the users explictly that firefox is not supported, instead of leaving the user much frustrated with a blank page.

@koenbok
Copy link
Owner

koenbok commented Feb 18, 2013

Fair point. I'll add some warning for now that points to this thread :-)

@jeffgca
Copy link

jeffgca commented Feb 18, 2013

I hacked a bit on a n experiment to use the CSSMatrix polyfill tonight:

jeffgca@003e505

It's a first step towards cross-browser support, but there are a bunch of other webkit-isms that would need to be generalized out or polyfilled.

@jfsiii
Copy link

jfsiii commented Apr 26, 2013

I have a project that attempts to polyfill CSSMatrix. In most cases, it is a drop-in replacement for WebKitCSSMatrix.

Take a look at the open issues, but it should work node.js and many versions of Chrome, Safari, Firefox, Opera. I haven't tested it in any versions of IE but "it's only Math". As I say in issue #2, I hope to soon have a browserling or other badge showing test results on various browsers.

My hope/plan for this weekend is to make the changes required to make Framer support non-WebKit browsers. I had a look around the source (which is how I found out about this ticket :) ) and (famous last words) it seems pretty straight forward.

@koenbok
Copy link
Owner

koenbok commented Apr 26, 2013

Sounds good to me. I'd like to say again though that supporting more browsers is not one of my primary goals. But people seem to want it, so I'll pull it in on the conditions that 1) there are no downsides/side effects and 2) the added code size is not crazy compared to the rest of the code.

@jfsiii
Copy link

jfsiii commented Apr 26, 2013

Great.

I'll make sure all existing tests continue to pass. If possible, I'll do a client-side check for WebKitCSSMatrix and only load XCSSMatrix if it's missing. Not sure if it is, but I'll give it a shot.

@rsms
Copy link

rsms commented May 15, 2013

FYI landed @jfsiii's patch in UILayer at rsms/uilayer@69caece

@nvh
Copy link
Collaborator

nvh commented Aug 3, 2016

This has been a while ago, and Firefox has decided to implement WebKitCSSMatrix. It already works in the Devoper preview, and is expected to land in 48. I'm closing this issue for now, as we're not expected to put any work into Firefox support until this lands in their stable.

@nvh nvh closed this as completed Aug 3, 2016
eelco pushed a commit that referenced this issue Sep 30, 2016
Add test for base64 encoded images
nvh pushed a commit that referenced this issue Jun 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants