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
ensure all DocumentFragment parse methods take ParseOptions and an options-configuration block #1844
Milestone
Comments
This was referenced Dec 16, 2018
Closed
Does this only apply for parsing http fragments or did I miss he change for Nokogiri::XML::DocumentFragment.parse ? |
@GreSuh thanks for asking this question. From the description above:
Hope this response helps. |
See #2399 for an updated version of this branch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See #1692 for the beginning of this work on HTML::DocumentFragment
See #1843 for a rebase of this work onto a modern
master
See branch
1844-fragment-parse-options-overhaul
for the start of adding tests to HTML::DocumentFragment which are more thorough than the current test approachThings I'd like to do as a result of this issue:
#read_io
,#read_memory
) save the ParseOptions as a Document attribute, to make testing a bit easierThe text was updated successfully, but these errors were encountered: