-
Notifications
You must be signed in to change notification settings - Fork 20.6k
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
Don't expose jQuery.dir & jQuery.sibling #2512
Comments
mgol
changed the title
Remove jQuery.dir & jQuery.sibling
Don't expose jQuery.dir & jQuery.sibling
Jul 31, 2015
mgol
added a commit
to mgol/jquery
that referenced
this issue
Aug 3, 2015
jQuery.dir & jQuery.sibling are undocumented internal APIs; they shouldn't be exposed. Fixes jquerygh-2512
mgol
added a commit
to mgol/jquery
that referenced
this issue
Aug 3, 2015
jQuery.dir & jQuery.sibling are undocumented internal APIs; they shouldn't be exposed. Fixes jquerygh-2512 Closes jquerygh-2525
PR: #2525 |
mgol
added a commit
to mgol/jquery
that referenced
this issue
Aug 6, 2015
jQuery.dir & jQuery.sibling are undocumented internal APIs; they shouldn't be exposed. Fixes jquerygh-2512 Closes jquerygh-2525
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have a few more undocumented APIs shipped under the jQuery object; two of them are
jQuery.dir
&jQuery.sibling
.Is there any reason why they should be exposed & undocumented? We should minimize the number of such cases as we did with
jQuery.swap
(#2058),jQuery.buildFragment
(#2224) &jQuery.domManip
(#2225).See also #2513.
The text was updated successfully, but these errors were encountered: