Skip to content

Make jQuery.support warning scarier and remove more properties #315

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

Closed
dmethvin opened this issue Jun 1, 2013 · 3 comments · Fixed by #366
Closed

Make jQuery.support warning scarier and remove more properties #315

dmethvin opened this issue Jun 1, 2013 · 3 comments · Fixed by #366

Comments

@dmethvin
Copy link
Member

dmethvin commented Jun 1, 2013

http://bugs.jquery.com/ticket/13977

http://bugs.jquery.com/ticket/13743

@mgol
Copy link
Member

mgol commented Sep 2, 2013

Why not remove all properties and just leave a scary warning?

mgol added a commit to mgol/api.jquery.com that referenced this issue Sep 10, 2013
Since jQuery.support is an unstable interface not intended for public use,
it's better to not describe it and make it easier for others to (mis)use.
This commit removes examples and changes text that might urge others
to try to rely on jQuery.support.
@mgol
Copy link
Member

mgol commented Sep 10, 2013

Look at my pull request. One jQuery user has already said on IRC he was misadvised by a note on jQuery.browser that tells user to depend on $.support instead of $.browser whereas they should do neither. We should remove all that information ASAP.

@mgol mgol closed this as completed in b7e4122 Sep 16, 2013
@OpenSorceress
Copy link
Contributor

(I forgot these even exist, tbh.)
On Sep 1, 2013 8:14 PM, "Michał Gołębiowski" notifications@github.com
wrote:

Why not remove all properties and just leave a scary warning?


Reply to this email directly or view it on GitHubhttps://github.com//issues/315#issuecomment-23637012
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

3 participants