Closed kris-lab closed 8 years ago
Please add a link to the PR and to the commit where the changes were applied in our project.
See also: Pull request: https://github.com/ftlabs/fastclick/pull/103 CM commit: https://github.com/kris-lab/CM/commit/054508f5d50a6dd2972f54aa8b6ae6965b3dee9c
@kris-lab can you also add a short description why we did https://github.com/ftlabs/fastclick/pull/103 in there, and maybe link it to their issue they have, to make their life easier, and increase the chances of getting it merged?
@kris-lab There were some discussion about this and ftlabs/fastclick#289 PR was done already. This PR solves our problem and it is made from fresh master, so it doesn't require additional merging. I guess now Fastclick's author waits for your response on your PR. So could please just write there that you prefer to close your PR in favor of the new one.
@kris-lab any news on this one?
Hard to say. let's wait if is done what here https://github.com/ftlabs/fastclick/pull/103#issuecomment-53962054
We are waiting for ftlabs/fastclick#289 I think it would be much faster to create our patched fastclick and use it until ftlabs/fastclick#289 is merged
@tomaszdurka So what do you think about using our own patched version.
@vogdb we are using a patched version, see: https://github.com/cargomedia/CM/blob/master/client-vendor/after-body/fastclick/fastclick.js#L1
This issue is just to track the progress of getting it merged upstream. So hopefully one day we can go back to the original upstream version. (the problem we custom patched versions is that sometimes when we upgrade the library it gets forgotten to patch it again..)
Sorry. I didn't see that.
I guess we will never see the patch =( ftlabs/fastclick#308
It's now in https://github.com/ftlabs/fastclick/pull/308 ;)
We're not using FastClick anymore.