Closed cekvenich closed 5 years ago
Hmm, I'm not sure where the source of https://sizzlejs.com/ is located. Can anyone else in @jquery/core help?
I haven’t heard about this domain before but this behavior is not related to Sizzle, https://wiki.github.com/ behaves in the same way. Closing.
@cekvenich Where did you get this URL from?
This should not be closed. On https://sizzlejs.com the documentation link is not working! Please reopen.
That is the original site for Sizzle and was created by the jQuery team years ago. But I don't know where the source lives. It could honestly be ftp'd to some www folder. However, I don't think anyone is being led astray by that broken link. If you try to find Sizzle, you'll be led here.
You are lead to the home page, and the first thing one would click is documentation - that is the broken link we are talking about. Seem like you should be able to get a handle to the DNS from the jquery team - now that their blog has said they will remove sizzle from jquery 4.0.
I'd be happy to fix the link, but someone more familiar with that website will need to help out (maybe @scottgonzalez or @gnarf?).
By the way, you're talking to the jQuery team. The site is old enough that it predates all of us.
Reopening since we now have an issue to resolve: fixing the link on the home page.
@gibson042 @timmywil BTW, the page is so old I think it'd be better to just redirect it to https://github.com/jquery/sizzle/wiki, removing the reference to the home page from that wiki. Maybe the discussion group should be archived as well, there hasn't been any posts there for more than 8 years.
Yea, we should remove the link to the google group.
Pinging more cool people @dmethvin @jquery/infrastructure @jquery/core-admin
I think it's on a digital ocean droplet (simple-sites.ops.jquery.net) - no telling what the password is on that thing though
Do we want to maintain that site? If not, we could just redirect the DNS to the Wiki and not try to track it down.
@dmethvin I proposed exactly that in my comment above. :)
Some additional context: people can be led to https://sizzlejs.com because it is linked from a few different places on https://jquery.com, like the icon in the top header bar.
@NReilingh Good point. Since we plan to retire Sizzle soon, perhaps we should remove that link from the jQuery site.
We still want to fix the DNS.
Curious @Mgol anywhere to follow along where v.4 is at timeline wise (removal of Sizzle)? Tnx
@Mapiac No specific timeline but I have a WIP PR (https://github.com/jquery/jquery/pull/4395) that first inlines Sizzle in jQuery & then removes all obsolete workarounds etc. This will be the first step, later on we'll simplify the code further, removing manual traversal code. But after the mentioned PR runs all the code used in jQuery will be directly in the jQuery repository; code from this Sizzle repo will only be used on the 3.4-stable
branch.
I've just merged another PR that ports most Sizzle tests to jQuery so that we don't miss anything when doing the refactor: https://github.com/jquery/jquery/pull/4406.
The redirect is in place!
https://wiki.github.com/jquery/sizzle
It says bad browser request.