Skip to content

CssSelector should be configured properly when used for HTML or XML #8404

@fabpot

Description

@fabpot

... but that's not really possible when using it from BrowserKit as the Crawler is created directly.

From #8286:

In functional test, since the crawler is instanciated by the de browser kit (which 
know the content-type), Can we imagine the browser kit call for us
disableHtmlExtension or enableHtmlExtension

Metadata

Metadata

Assignees

No one assigned

    Labels

    CssSelectorDomCrawlerGood first issueIdeal for your first contribution! (some Symfony experience may be required)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions