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.

Sign up for GitHub

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

Jump to bottom

use Nokogiri's parse_noscript_content_as_text option by default if it's available #285

Open
flavorjones opened this issue Jun 20, 2024 · 1 comment
Open

use Nokogiri's parse_noscript_content_as_text option by default if it's available #285

flavorjones opened this issue Jun 20, 2024 · 1 comment

Comments

@flavorjones
Copy link
Owner

See sparklemotion/nokogiri#3231 and sparklemotion/nokogiri#3178 for context.

This is yet another step towards making the server and browser parse identically.

The Nokogiri 1.17 milestone can be followed at https://github.com/sparklemotion/nokogiri/milestone/31 or the tracking issue at sparklemotion/nokogiri#3140
@flavorjones
Copy link
Owner Author

v1.17.0 landed today, I'll try to schedule some work on this.

@flavorjones flavorjones changed the title placeholder: when Nokogiri 1.17 is released, use the parse_noscript_content_as_text option by default use Nokogiri's parse_noscript_content_as_text option by default if it's available Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@flavorjones