We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Problem Description In certain circumstances, it's useful to grab computed styles from a page. Currently, this is impossible via fire crawl
Proposed Feature
Firecrawl returns a computed styles object when a parameter is passed
Alternatives Considered Is there a way for us to pass through more p
Implementation Suggestions Playwright has a "getComputedStyle" method https://developer.mozilla.org/en-US/docs/Web/API/Window/getComputedStyle. However, Idk if this would work without a traversal. There may be an easier way
Use Case This would be useful for situations where the computed styles matter. Such as web agents or A/B testing tools
Additional Context
When complete, notify GB via slack @calebpeffer
The text was updated successfully, but these errors were encountered:
Marking as blocked for now as not needed immediately.
Sorry, something went wrong.
No branches or pull requests
Problem Description
In certain circumstances, it's useful to grab computed styles from a page. Currently, this is impossible via fire crawl
Proposed Feature
Firecrawl returns a computed styles object when a parameter is passed
Alternatives Considered
Is there a way for us to pass through more p
Implementation Suggestions
Playwright has a "getComputedStyle" method https://developer.mozilla.org/en-US/docs/Web/API/Window/getComputedStyle. However, Idk if this would work without a traversal. There may be an easier way
Use Case
This would be useful for situations where the computed styles matter. Such as web agents or A/B testing tools
Additional Context
When complete, notify GB via slack @calebpeffer
The text was updated successfully, but these errors were encountered: