Skip to main content

Bug Tracker

Side navigation

#10849 closed bug (invalid)

Opened November 21, 2011 10:02PM UTC

Closed December 06, 2011 07:54AM UTC

Last modified March 14, 2012 10:43AM UTC 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:

According to the docs (and verified by taking a quick look at the source), 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 and

Attachments (0)
Change History (3)

Changed November 21, 2011 10:32PM UTC by dmethvin comment:1

owner: →
status: newpending

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 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?

Changed November 22, 2011 12:31AM UTC by Ryan Grove <> comment:2

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.

Changed December 06, 2011 07:54AM UTC by trac-o-bot comment:3

resolution: → invalid
status: pendingclosed

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!