jquery

sizzle

JavaScript2011–2024

jquery / sizzle

sizzle

A sizzlin' hot selector engine.

Explore on GitHub Read Hacker News discussions

15Distinct people

15Mentions

0Explicit recommenders

6.3KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

A sizzlin' hot selector engine.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

jquery/jquery · linked in 2 of the same discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year15 dated mentions

Observed mentions: 2011-04-12 04:39:30 UTC to 2024-10-25 06:53:04 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
2011	2011-01-01 00:00:00 UTC	2012-01-01 00:00:00 UTC	2	2
2012	2012-01-01 00:00:00 UTC	2013-01-01 00:00:00 UTC	0	0
2013	2013-01-01 00:00:00 UTC	2014-01-01 00:00:00 UTC	4	4
2014	2014-01-01 00:00:00 UTC	2015-01-01 00:00:00 UTC	1	1
2015	2015-01-01 00:00:00 UTC	2016-01-01 00:00:00 UTC	2	2
2016	2016-01-01 00:00:00 UTC	2017-01-01 00:00:00 UTC	3	3
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	0	0
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	1	1
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	0	0
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	0	0
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	0	0
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	0	0
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	1	1
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	1	1

What Hacker News says

15 sources

hnbad·Oct 25, 2024

Before `querySelectorAll` there was Sizzle, which was the selector engine that was eventually spun out of jQuery itself: https://github.com/jquery/sizzle If you think that's wild, before there were dev tools in every browser, there was only Firebug (yes, there was only `alert` before that, we didn't even have `console.log`): https://getfirebug.com/

In Two examples of hover styles on images

DaiPlusPlus·Jul 19, 2023

jQuery first came-out long before browsers had querySelector: it used a 100% JS reimplementation of a CSS selector parser and evaluator, which was eventually spun-off into its own library: Sizzle.js: https://github.com/jquery/sizzle - Surprisingly, jQuery didn't fully remove Sizzle until 2019 ( https://blog.jquery.com/2019/04/10/jquery-3-4-0-released/ ) - if that seems surprisingly recent, don't forget that querySelector wasn't added to the DOM API until 2013 - with only IE11 supporting it: some places were still using even IE6 well past then, so it makes sense for jQuery to support it for so long. So using newer CSS selector features, like attribute value selectors, will work fine in post-Sizzle jQuery versions.

In Tiffin Tom: Fish, chips and a side of identity theft

brailsafe·Jul 25, 2018

I think those are some broad generalizations that I can't agree with, but Sizzle might be what you're looking for. https://github.com/jquery/sizzle/wiki

In Removing jQuery from GitHub.com frontend

ubertaco·Jul 8, 2016

If by "standards-compliant" you mean "sometimes standards-compliant, and sometimes riddled with major, painful bugs" (including bugs that usually have already been patched upstream in Webkit long before the patches eventually trickle their way down into Safari). Pulling from a comment I posted over on Reddit recently: -- Looking back through my painful history of Safari headaches I've personally encountered in building a single-page app, at least it appears that there's some progress: * It looks like the pervasive, opaque, and seemingly-random "attempted to assign to readonly property" crap that affected only Safari and broke Angular, Ember, React, and others has been fixed, at least in upstream Webkit (https://bugs.webkit.org/show_bug.cgi?id=138038#c21). I guess we can take out our Safari-only monkey-patch fix now, so that's nice. Would

Read the rest

be nice if I could get that entire work week of debugging and workarounds back, but c'est la vie. Assuming, of course, that Safari has finally pulled this fix in from upstream, which is far from guaranteed. * Date parsing (http://stackoverflow.com/questions/4310953/invalid-date-in-s...) now behaves up to the standard, just like all other browsers; I suppose we no longer need to use Moment.js as "Safari's handicap access ramp" anymore either. * The broken multi-select bug (http://stackoverflow.com/questions/20039194/multiple-select-...) still seems sporadically there. * It's unclear whether they've fixed adjacent-element selectors in querySelector (https://github.com/jquery/sizzle/issues/290). It's been fixed in Webkit, so maybe in a year or so Safari will have it fixed too. This is just stuff I've seen in my normal day-to-day of a not-super-complex Angular single-page app. You can see, I'd hope, why I have plenty of room based on Safari's track record to assume their implementation of anything is subtly-but-painfully broken. Normally, I'd go check the status of these things on a bugtracker, but unlike the Chromium team, the Firefox team, or the Edge team, I guess the Safari team is just too perfect to need a publicly-accessible bugtracker. Or too embarrassed to have one? Yeah, it's one of those. Having a green (or more often, yellow-green) checkbox on caniuse or kangax doesn't mean the feature is usable, it just means it's technically available.

In Ask HN: Is Safari the new IE?

lollipop25·Mar 25, 2016

Are you aware that jQuery bundles Sizzle? I guess not. https://github.com/jquery/jquery#modules https://github.com/jquery/sizzle

In If you write JavaScript tools or libraries, bundle your code before publishing

jeresig·Jan 13, 2016

It does! https://github.com/jquery/sizzle/blob/master/dist/sizzle.js

In Lodash 4.0.0 is out

dansingerman·Aug 19, 2015

I know this is a famous meme, but why, in response, does no one mention that sizzle, the selector engine in jQuery is based on regexes? (https://github.com/jquery/sizzle/blob/master/src/sizzle.js) It suggests to me a very large proportion of DOM parsing code in existence uses regexes.

In Source of the famous “Now you have two problems” quote (2006)

dmethvin·Mar 26, 2015

Here are some I'm aware of: https://github.com/jquery/sizzle/issues/290 https://github.com/jashkenas/underscore/issues/2081 https://github.com/jquery/jquery/issues/2145 Webkit devs are aware of these and they have been fixed in Webkit core, but Apple doesn't provide any info about when the fixes may see the light of day.

In Intent to Implement: Pointer Events in Chrome

jcampbell1·Jan 30, 2014

> Also, last time I checked jquery uses "querySelectorAll" for that fancy $("selector") syntax, which is slow as hell with every possible browser compared to "getElementBy". I seriously doubt you ever "checked". You would know that jQuery's selector engine (Sizzle) is optimized and uses getElementBy* when it can. You would also know that every browser has bugs in querySelectorAll, and jQuery's selector engine detects the bugs and routes around the browser bugs. https://github.com/jquery/sizzle/blob/master/src/sizzle.js

In You might not need jQuery

wldlyinaccurate·Nov 12, 2013

> Even if Node was 5x slower than PHP I would still go for Node because of its easy jQuery syntax That "jQuery syntax" has nothing to do with the language itself. jQuery uses Sizzle[0], which is a CSS selector library for JavaScript. There are plenty of PHP libraries which provide CSS selectors, such as the Symfony CssSelector component[1]. [0] https://github.com/jquery/sizzle [1] https://github.com/symfony/CssSelector

In Benchmarking Codswallop: Node.js vs. PHP

mambodog·May 20, 2013

In the case of querySelectorAll, it does[1] (after performing some checks for easy wins) and if this test[2] is anything to go by, it can actually perform better in some cases. [1] https://github.com/jquery/sizzle/blob/master/sizzle.js#L237 [2] http://jsperf.com/yui3-vs-jquery-selector-test-3/54

In Native equivalents of jQuery functions

Schlaefer·May 20, 2013

Right from the source: "Sets document-related variables once based on the current document" [1]. It's a very readable document and the comments give good overview about quirks you have to be aware of. My personal opinion: not using jQuery (or similar library) for normal webpages is premature optimization and it will hurt more than help. [1] https://github.com/jquery/sizzle/blob/master/dist/sizzle.js#...

In Native equivalents of jQuery functions

k3n·Apr 29, 2013

Interesting, but I'm not sure how appropriate it is to be comparing it to jQuery in such a head-to-head fashion such as by saying "15x slower", etc. Does Dommy offer the same features (including the browser support) that jQuery does? If not, then you're just comparing apples to oranges, and it doesn't sound like it does (or even plans to) on account that it sounds like there are design decisions that separate the two with regards to the published API ("Inspired by jQuery, but adapted to be functional in order to better fit with ClojureScript core"). Also, wouldn't it be more accurate for the selector testing to actually test against Sizzle[1]? Other features aren't even present in jQuery, such as templating, and so I'm not sure why you'd even compare that. Yes people can and do use templates with jQuery, but that's an implementation detai

Read the rest

l and is not a concern of the library itself; jQuery does not coerce or force you to use a slow templating system, and most any good templating system will also have a compilation step that is run at build-time. So yeah, you can take some ugly userland jQuery example code and make specific code that is faster.. 1. https://github.com/jquery/sizzle

In Faster, Better DOM manipulation with Dommy and ClojureScript

autoreverse·Oct 5, 2011

Thanks for building Akayame bambax. Pretty neat. A few comments: 1) Please add one or more licenses so developers can include Akayame in their projects with confidence. A couple of examples: http://jquery.org/license/ https://github.com/jquery/sizzle/blob/master/LICENSE 2) The footer and menu are below the fold in my browsers in the Converter and Editor views so I need to scroll to see the menu and "Yet Another Markdown Editor" text. 3) The footer could do with improved styling : text overlaps the border, bullets and links use default styles. Minor quibbles but improvements would improve the professionalism of the site. Image here: http://autoreverse.s3.amazonaws.com/2011006_Akayame_footer.j... 4) Landing page does not convey to the visitors what the site is about (and"Yet Another Markdown Editor" is below the fold). 5) Adding a page or t

Read the rest

wo with keyword rich text explaining the project ("jQuery powered online Markdown editor") and background ("inspired by other Showdown online Markdown editor projects") could help with search engines listings. 6) Have you considered hosting the code on Github for increased exposure and link juice?

In Learning from my web app 23 visits at a time

freakwit·Apr 12, 2011

You're being disingenuous here. Anybody looking for information about jQuery's selectors will google "jquery selectors" and find that five-word phrase front and center. Or take a look at the jQuery front page and hover over "CSS3 Compliant" to see "Supports CSS 1-3 selectors and more!". If you want to pick on something that claims compatibility, try Sizzle itself - http://sizzlejs.com/. In that case, you'll find a summary of alterations right at the top of its documentation https://github.com/jquery/sizzle/wiki .

In The jQuery Divide:Understand where jQuery ends and JavaScript begins