Conversation
laybxc
marked this pull request as draft
September 7, 2026 14:03
laybxc
force-pushed
the
fix/weixin-drag-verification-detection
branch
from
September 7, 2026 15:53
4b6280b to
2b9e6ea
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
weixin downloadusespage.wait(5)before extraction. Numericwaitcan return after just 500 ms of DOM quietness, allowing an empty loading shell to reach extraction before the article arrives.Poll the same tab for a parsed document, an article URL, a title and non-empty
#js_content(text or media). The adapter owns its single navigation, skipping the Official Account homepage. Extraction cleans a clone without modifying the live page, and metadata is extracted only once content is ready.The readiness loop uses a 15-second budget after navigation. Browser requests retain their existing transport timeout and errors; there is no additional RPC timeout wrapper. An in-flight request can exceed the readiness budget, but a late response is neither downloaded nor followed by another probe.
Explicit verification interaction prompts retain the existing failure result. Other incomplete pages raise
TIMEOUT; intermediate URLs and opaque iframes are not classified as verification failures. Pages may advance naturally while waiting, without refresh, URL rewriting or CAPTCHA interaction. Readiness means extractable content is present, not that all dynamically appended content or media have finished loading.Related: #2045. This addresses premature extraction; it does not establish that the challenge in that report resolves without interaction. #1770's stdout work is separate.
Type of Change
Checklist
Validation
OPENCLI_CONFIG_DIR: 632 files, 7336 tests passed, 1 skipped. The full suite was not rerun for this scoped simplification.This remains a draft.