#10849 closed bug (invalid)
jQuery.support.hrefNormalized means the opposite of what its name implies
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | undecided | Milestone: | None |
Component: | unfiled | Version: | 1.7.1rc1 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
According to the docs (and verified by taking a quick look at the source), jQuery.support.hrefNormalized will be true if hrefs are *not* normalized, and false if they are.
This is the opposite of what the name implies, which is confusing.
See http://api.jquery.com/jQuery.support/ and https://github.com/jquery/jquery/blob/master/src/support.js#L56
Change History (3)
comment:1 Changed 12 years ago by
Owner: | set to ryan@… |
---|---|
Status: | new → pending |
comment:2 Changed 12 years ago by
I don't have plans to use it; just happened to notice the confusing name. I agree that changing the name would be a reasonable solution, although "hrefNotNormalized" is a little unwieldy. Maybe someone has a better suggestion.
comment:3 Changed 11 years ago by
Resolution: | → invalid |
---|---|
Status: | pending → closed |
Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!
In general, the feature detects are set so they are false for browser that are a pain in the butt. So by that measure it's got the right value, perhaps it has the wrong name.
We have contemplated taking the entire jQuery.support object to deprecation land because we do not want to support specific properties as an external interface if we do not need them. Were you just observing that it seemed backwards, or are you planning to use it?