Closed th507 closed 11 years ago
Nice work!
Although, for consistency with the other APIs, I'd prefer:
fastdom.defer(<callback>, <frames>, <context>);
I agree splitting context as a separate parameter is a plus for consistency, but separating callback
and context
with another irrelevant parameter is perhaps not entirely coherent. If compatibility is not an issue, I would suggest
fastdom.defer(<frames>, <callback>, <context>);
However, if maintain compatibility is a priority for this project, I could make changes according to your suggestion.
I completely agree, let's go with your suggestion :) On 25 Sep 2013 03:27, "Jingwei Liu" notifications@github.com wrote:
I agree splitting context as a separate parameter is a plus for consistency, but separating callback and context with another irrelevant parameter is perhaps not entirely coherent. If compatibility is not an issue, I would suggest
fastdom.defer(
, , ); However, if maintain compatibility is a priority for this project, I could make changes according to your suggestion.
— Reply to this email directly or view it on GitHubhttps://github.com/wilsonpage/fastdom/pull/13#issuecomment-25058196 .
proposed fix for #12