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

Improved compatibility with "How Many Times Can I Back?" (#397) #554

Merged
merged 2 commits into from
Sep 12, 2013

Conversation

wanabe
Copy link
Contributor

@wanabe wanabe commented Sep 12, 2013

"getCommonAncestor" method is not available without jQuery

"getCommonAncestor" method is not available without jQuery
@piroor
Copy link
Owner

piroor commented Sep 12, 2013

Oops, I think I wanted to use DOMRange#commonAncestorContainer.
http://www.w3.org/TR/DOM-Level-2-Traversal-Range/ranges.html#Level-2-Range-attr-commonParent
Could you rewrite your patch based on it?

let container = containerFinder.getCommonAncestor();
let containerFinder = namedNodes.closeAnchor;
let containers = [];
while (containerFinder != aTab) {
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In this project, I use the style:

while (...)
{

instead of

while (...) {

for "while", "for", "switch" blocks. So, in the future, please fit your patch to existing styles ;-)

@piroor
Copy link
Owner

piroor commented Sep 12, 2013

One more. I basically use "git style" for commit messages in this project.
https://github.com/gitster/git/blob/master/Documentation/SubmittingPatches
So, "Improve compatibility..." is better.

use commonAncestorContainer instead of getCommonAncestor()
@wanabe
Copy link
Contributor Author

wanabe commented Sep 12, 2013

Oh, sorry.
I rewrote the patch and commit log.

piroor added a commit that referenced this pull request Sep 12, 2013
Improved compatibility with "How Many Times Can I Back?" (#397)
@piroor piroor merged commit d045439 into piroor:master Sep 12, 2013
@piroor
Copy link
Owner

piroor commented Sep 12, 2013

Thanks a lot!

BTW, I hope you to cancel the old pull request (like this) and re-send new pull request without unnecessary commit (like 1a83376), In the next time.

@kou
Copy link

kou commented Sep 12, 2013

You can rewrite commit message without creating a new pull request by git commit --amend and git push -f.

@wanabe
Copy link
Contributor Author

wanabe commented Sep 12, 2013

Thank you for all of the advice!
I'll be careful in the future.

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.

3 participants