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
Moving back to upstream selectors
?
#729
Comments
I'd love to do that. The reasons for the fork were:
If you have any ideas on whether some of these could be supported, either up stream or otherwise via extension, I'd love to make it work. |
@emilio Would you be willing to accept such changes (appropriately feature flagged if necessary) into upstream |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Development on the Servo project has been picking up recently, and one of the things we're looking at is improving the maintenance of it's crates (including
selectors
which now lives in https://github.com/servo/stylo) and trying to merge back forks and pool development effort back into the original crates.I am wondering:
selectors
?selectors
? (and would you be interested in doing this)?selectors
?selectors
is a little complicated than some crates because upstream is actually Mozilla's Firefox repository (currently still using mercurial), but we have / are putting in place a process for coordinating with Gecko developers and syncing changes with Gecko.The text was updated successfully, but these errors were encountered: