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

Leverage 2009 spec where present? #17

Closed
pci opened this issue Mar 15, 2013 · 3 comments
Closed

Leverage 2009 spec where present? #17

pci opened this issue Mar 15, 2013 · 3 comments

Comments

@pci
Copy link
Collaborator

pci commented Mar 15, 2013

This has probably been looked at before, but could we use the 2009 display: box; support to do some of the positioning heavy lifting if it's present? It would minimise CPU and render time to leverage existing browser code.

Caniuse suggests 30% of desktop users and over 80% of mobile users support the 2009 syntax. For basic use (flex, order and direction) compatibility looks fairly good, and if it's more advanced than that we could always fall back to reflexie doing all the work.

The main question seems to be: How bad would the edge cases be? Is there a subset of features that we could safely transcribe to the 2009 spec?

@doctyper
Copy link
Owner

Well, there's always a chance that browsers will eventually pull the old flexbox code from their codebase.

What I'd like to do is finish the polyfill without a dependency on the old flexbox model. After that milestone we can revisit bridging the models to take advantage of existing functionality. That way, even if old flexbox goes away Reflexie will still be able to polyfill them.

@pci
Copy link
Collaborator Author

pci commented Mar 15, 2013

Sorry, I don't think I've explained myself well. I was more thinking
if(new spec supported): return
elseif(old spec supported and basic usage): translate css to old spec
else: full reflexie

But you're right, finishing the polyfill before looking at optimisations is the way to go. Do you want me to close the issue or leave it open for the far-future?

Also, what's a good job/issue to get started on and get used to the code?

@pci
Copy link
Collaborator Author

pci commented Mar 27, 2013

Closed as not relevant

@pci pci closed this as completed Mar 27, 2013
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

2 participants