Skip to content

Conversation

@todorpr
Copy link
Contributor

@todorpr todorpr commented Jan 25, 2016

Since v2.2.0: Cannot read property 'opener' of null when $.parseHTML and then get css style #2866

@mention-bot
Copy link

By analyzing the blame information on this pull request, we identified @mr21, @markelog and @timmywil to be potential reviewers

@jquerybot
Copy link

Thank you for your pull request. It looks like this may be your first contribution to a jQuery Foundation project, if so we need you to sign our Contributor License Agreement (CLA).

📝 Please visit http://contribute.jquery.org/CLA/ to sign.

After you signed, the PR is checked again automatically after a minute. If there's still an issue, please reply here to let us know.


If you've already signed our CLA, it's possible your git author information doesn't match your CLA signature (both your name and email have to match), for more information, check the status of your CLA check.

Copy link
Member

Choose a reason for hiding this comment

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

Space after (.

@timmywil
Copy link
Member

Thanks! If we can figure out a unit test, that would be great.

@gibson042
Copy link
Member

I like to see a test case added. http://jsbin.com/ruyecuxogu/edit?html,js,console,output would make a fine base (.css on an element created by jQuery.parseHTML with nontrivial input).

@todorpr
Copy link
Contributor Author

todorpr commented Jan 26, 2016

@timmywil I don't know what else to do to resolve this CLA error. I did the changes in my pull request directly in Github. Then when I filled in the CLA form and got the error I realized that I didn't have full name in my Github account. Then I filled my full name in Github, but the CLA error still remains. Finally I followed the instructions to update the git config, i.e:

git config --global user.name "YOUR NAME"
git config --global user.email "[email protected]"

and then:

# Switch to your branch
git checkout your-branch-name

# Amend the commit, setting the author based on your updated git config
git commit --amend --reset-author

# Push the amended commit to your fork
# Because the amended commit changed history, you need to force push (-f)
git push -f your-remote your-branch-name

still no luck.

@mgol
Copy link
Member

mgol commented Jan 26, 2016

@todorpr You have 2 commits in your PR and you amended only one. Can you squash them to one & try again?

@todorpr
Copy link
Contributor Author

todorpr commented Jan 26, 2016

@mgol
Copy link
Member

mgol commented Jan 26, 2016

@todorpr You didn't squash it as the branch still contains a merge commit; this is how a Git tree looks like right now (pr/2867 is your branch):
screen shot 2016-01-26 at 12 16 45
You may also run:

git log --graph

in a console to see the tree in text mode.

It's best to avoid merges when working on something; you probably merged master to your branch which caused all those problems; you should be rebasing over master instead.

At this point it's easiest to run:

git reset --soft master

which will remove all your commits but keep the changes. You can then commit the change again, just copy the commit description somewhere so that you can paste it.

@todorpr
Copy link
Contributor Author

todorpr commented Jan 26, 2016

@mgol thanks, it's good now. Finally had to git push -f to update the repo.

timmywil added a commit to timmywil/jquery that referenced this pull request Jan 27, 2016
@timmywil timmywil closed this in 35c3148 Jan 27, 2016
timmywil pushed a commit that referenced this pull request Jan 27, 2016
timmywil added a commit that referenced this pull request Jan 27, 2016
timmywil pushed a commit that referenced this pull request Jan 27, 2016
timmywil added a commit that referenced this pull request Jan 27, 2016
@lock lock bot locked as resolved and limited conversation to collaborators Jan 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Development

Successfully merging this pull request may close these issues.

6 participants