← Back to microsoft/playwright
microsoft / playwright · Issue No. 42077
find returns the whole ancestor chain of the match, so most of the output is wrapper nodes rather than the thing found. Searching a job board for one heading gave me eight levels of generic [ref=eN] to deliver three useful lines:
- generic [ref=e2]:
- generic [ref=e8]:
- generic [ref=e12]:
- generic [ref=e26]:
- generic [ref=e72]:
- link [ref=e73] [cursor=pointer]:
- /url: /pangramlabs/64baa007...
- generic [ref=e74]:
- heading "AI Research Scientist (NLP)" [level=3] [ref=e75]
For agent use this matters because the output is the context budget. A mode that returns the matched node plus its immediate children, without the path back to root, would cut that several-fold.
Related, there is no way to bound the output when a query is common: no --max-results on find, and no depth limit on snapshot, so a deeply nested SPA produces a large tree when two levels would do. Version 0.1.17.
Relay reads this issue against the repository's contribution signals: the files it is likely to touch, how the maintainers triage work this size, and what the first contribution would exercise.
The full analysis for this issue is still being assembled. Until then, the description above and the thread on GitHub are the most reliable context.