The CssSelector ComponentEdit this page
Warning: You are browsing the documentation for Symfony 3.4, which is no longer maintained.
Read the updated version of this page for Symfony 6.2 (the current stable version).
The CssSelector component converts CSS selectors to XPath expressions.
$ composer require symfony/css-selector:^3.4
If you install this component outside of a Symfony application, you must
vendor/autoload.php file in your code to enable the class
autoloading mechanism provided by Composer. Read
this article for more details.
This article explains how to use the CssSelector features as an independent component in any PHP application. Read the Symfony Functional Tests article to learn about how to use it when creating Symfony tests.
When you're parsing an HTML or an XML document, by far the most powerful method is XPath.
XPath expressions are incredibly flexible, so there is almost always an XPath expression that will find the element you need. Unfortunately, they can also become very complicated, and the learning curve is steep. Even common operations (such as finding an element with a particular class) can require long and unwieldy expressions.
Many developers -- particularly web developers -- are more comfortable
using CSS selectors to find elements. As well as working in stylesheets,
CSS selectors are less powerful than XPath, but far easier to write, read and understand. Since they are less powerful, almost all CSS selectors can be converted to an XPath equivalent. This XPath expression can then be used with other functions and classes that use XPath to find elements in a document.
The component's only goal is to convert CSS selectors to their XPath equivalents, using toXPath():
1 2 3 4
use Symfony\Component\CssSelector\CssSelectorConverter; $converter = new CssSelectorConverter(); var_dump($converter->toXPath('div.item > h4 > a'));
This gives the following output:
descendant-or-self::div[@class and contains(concat(' ',normalize-space(@class), ' '), ' item ')]/h4/a
Not all CSS selectors can be converted to XPath equivalents.
There are several CSS selectors that only make sense in the context of a web-browser.
- link-state selectors:
- selectors based on user action:
- UI-state selectors:
:first-letter) are not supported because they select portions of text
rather than elements.
Several pseudo-classes are not yet supported:
*:only-of-type. (These work with an element name (e.g.
li:first-of-type) but not with