Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTML parsing options #74

Merged
merged 5 commits into from
Feb 9, 2015
Merged

HTML parsing options #74

merged 5 commits into from
Feb 9, 2015

Conversation

goetas
Copy link
Member

@goetas goetas commented Jan 18, 2015

Closes #69

This change has to be integrated

@goetas goetas changed the title Feature/html parsing options HTML parsing options Jan 18, 2015
jslegers and others added 2 commits February 6, 2015 22:07
flexible HTML DOM creation.

New Options:

* disableHtmlNsInDom = Allows the use of createElement instead of
createElementNS for HTML elements.

* targetDocument = allows an existing DOMDocument (or subclass thereof)
to be passsed to the DOMTreeBuilder instead of creating a new one.
@goetas goetas force-pushed the feature/html-parsing-options branch from 8d51ad4 to a5f8b8c Compare February 6, 2015 21:10
@goetas goetas force-pushed the feature/html-parsing-options branch from effaccd to a50e919 Compare February 6, 2015 21:19
@goetas
Copy link
Member Author

goetas commented Feb 6, 2015

@mattfarina @technosophos On monday i'm planning to merge this and release the 2.1.0 version. Any thoughts?

//cc @jslegers

@coveralls
Copy link

Coverage Status

Coverage increased (+0.01%) to 89.05% when pulling a50e919 on feature/html-parsing-options into dda3253 on master.

goetas added a commit that referenced this pull request Feb 9, 2015
@goetas goetas merged commit 236faa2 into master Feb 9, 2015
@goetas goetas deleted the feature/html-parsing-options branch February 9, 2015 16:26
* `disable_html_ns` (boolean): Prevents the parser from automatically
assigning the HTML5 namespace to the DOM document. This is for
non-namespace aware DOM tools.
* `target_doc` (\DOMDocument): A DOM document that will be used as the
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just noticed this: the code expects 'target_document' but the docs say 'target_doc', which shall we change to make it consistent?

@goetas
Copy link
Member Author

goetas commented Feb 9, 2015

@cognifloyd fixed on master, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants