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

Support non-WebKit browsers #5

Merged
merged 11 commits into from
May 15, 2013
Merged

Support non-WebKit browsers #5

merged 11 commits into from
May 15, 2013

Conversation

jfsiii
Copy link
Contributor

@jfsiii jfsiii commented Mar 19, 2013

I doubt this is ready to be merged just yet, but I wanted to get a discussion going about what I've done so far.

John Schulz and others added 11 commits March 9, 2013 16:33
 * `lookupCSS` and `lookupJS' accept the non-prefixed property name and returns the supported property name. Return values are either vendor-prefixed, not-prefixed, or `false` if it's unsupported
 * `lookupCSS` accepts a dashed CSS property value (like `box-sizing') and `lookupJS` accepts a camel case string (like `boxSizing`). It would be trivial to implement versions which accepted multiple argument types and returned the correct value, but punting on that until it's needed.
 * The lookup table (for both JS and CSS values) is generated at "compile-time" based on a list of values known to be used. The `lookup*` functions could be altered to do lazy loading if desired. That approach was avoid in this initial version to avoid any run-timeperformance penalty.
FF (19, at least) does not support the individual transform-origin properties (e.g, `transform-origin-x`, `transform-origin-y`). Neither prefixed nor otherwise.

Using the shorthand property gets around this limitation and, I think, could be faster because there are fewer operations.
Links were all 'undefined'. Use jQuery, in lieu of DOM methods, since we
already load it in the page for XHR.
rsms added a commit that referenced this pull request May 15, 2013
Support non-WebKit browsers. Amazing work by @jfsiii.
@rsms rsms merged commit 69caece into rsms:master May 15, 2013
@jfsiii
Copy link
Contributor Author

jfsiii commented May 15, 2013

I'm stoked to see this merged.

Should we edit README.md to replace references to WebKit with something more accurate (e.g, 'browsers which support both CSS Transforms and Transitions')?

@rsms
Copy link
Owner

rsms commented May 15, 2013

Good point.

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

Successfully merging this pull request may close these issues.

2 participants