Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[Bug]: cleaned_html drops the page body when it is nested inside an unclosed <noscript>

未关闭
#2,293 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
58/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
python
领域
backend, web-dev

调研方向

Start with LXMLWebScrapingStrategy._scrap in the content scraping strategy and run the offline reproduction from the issue. Compare cleaned_html with result.html for unbalanced nested noscript tags; done means the body content remains while noscript fallback blocks are still removed. Check issue #2284 because the report says a fix is proposed there.

由索引模型根据 Issue 内容生成。

描述

crawl4ai version

0.9.4 (develop @ 86e6464); also reproduced on 0.9.0

Expected Behavior

cleaned_html keeps the page's body content. <noscript> fallback blocks are removed, as they are today.

Current Behavior

On pages that contain nested <noscript>, cleaned_html loses part or all of the body, even though result.html contains the full page.

Lazy-load plugins commonly wrap an existing noscript (typically Google Tag Manager's), so the served page contains:

<noscript><iframe ...></iframe><noscript><iframe src="https://www.googletagmanager.com/ns.html?id=..."></iframe></noscript></noscript>

The browser has scripting enabled, so it treats noscript contents as raw text and ends the element at the first </noscript>. The stray second closing tag is dropped when page.content() serializes the DOM, so the capture has more opening tags than closing ones. lxml parses with scripting disabled, so it nests the rest of the document inside the still-open <noscript>, and LXMLWebScrapingStrategy._scrap then deletes that content when it removes noscript elements.

One common source is LiteSpeed Cache's iframe lazy-load (~7M active WordPress installs), which rewrites GTM's noscript iframe this way: WordPress.org support thread.

Visible text in cleaned_html for affected pages, default configs (2026-09-24):

Page noscript open/close in capture Visible chars in cleaned_html Visible chars in result.html
https://www.comunio.es/ 5 / 4 0 ~4,000
https://halalvlees.nl/ 5 / 4 1,834 12,480
https://www.dietdoctor.com/ 63 / 54 7,846 8,171

In a random sample of 2,972 Tranco top-1M homepages (ranks 20k–1M), 6 served nested noscript, and 4 of those lost content this way.

Is this reproducible?

Yes

Inputs Causing the Bug
- URL(s): https://www.comunio.es/ , https://halalvlees.nl/
- Settings used: defaults (BrowserConfig(), CrawlerRunConfig())
- Input data: any HTML with more <noscript> opening tags than closing tags
Steps to Reproduce
1. Crawl https://www.comunio.es/ with default settings
2. Compare result.cleaned_html with result.html
3. cleaned_html has an empty body; result.html has the full page
Code snippets
# Offline repro: the shape page.content() produces for such a page
from crawl4ai.content_scraping_strategy import LXMLWebScrapingStrategy

html = """<html><head><title>Example shop</title></head><body>
<noscript><iframe src="about:blank"></iframe><noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-TEST"></iframe></noscript>
<div><h1>Real heading</h1><p>Real body copy.</p></div>
</body></html>"""

print(LXMLWebScrapingStrategy().scrap("https://example.com/", html).cleaned_html)
# Actual:   <html><head><title>Example shop</title></head></html>
# Expected: the <h1> and <p> are kept
# Live repro
import asyncio
from crawl4ai import AsyncWebCrawler

async def main():
    async with AsyncWebCrawler() as crawler:
        result = await crawler.arun("https://www.comunio.es/")
        print(len(result.html), repr(result.cleaned_html[-200:]))

asyncio.run(main())
OS

macOS 26.6 (arm64)

Python version

3.12.11

Browser

Chromium (Playwright headless shell)

Browser version

153.0.8010.12

Error logs & Screenshots (if applicable)

No error is raised; result.success is True and the status code is 200.

A fix is proposed in #2284.

主要语言
Python
星标
84.5k
派生
8.7k
平均合并
3 天 9 小时
30 天内合并 PR
17

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

unclecode/crawl4ai 的其他 Issue

查看 unclecode/crawl4ai 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。