-
I switched over from `heroku/google-chrome` this week and followed the instructions on [Migrating from Separate Buildpacks](https://github.com/heroku/heroku-buildpack-chrome-for-testing?tab=readme-ov-…
-
# Ferrum 2.0 计划
Ferrum Explorer其实是我几年前的项目了,本来计划不再更新Ferrum,现在想重新启动这个项目,以下是一些计划。
## 起因 / 问题
1. 在编写Ferrum 1.0版本的时候,由于本人技术水平有限,故无法制作出架构合理且布局美观的app。
2. Ferrum 1.0是基于React 17版本的客户端渲染,而非React服务端渲染(…
-
need set up this actions:
Build Ferrum on linux,
Build Ferrum on windows
Run all tests on linux
Run golangci linters
trigger is the pushing into 'develop' and 'master' branches
-
### Describe the bug
Our Ferrum script starts having process_timeout errors after upgrading to the [Heroku/Chrome-for-testing buildpack](https://github.com/heroku/heroku-buildpack-chrome-for-testing)…
-
If you initialize Ferrum with a window size using remote browserless 2 - the window size is applied, but the viewport is not updated automatically. The DOM is rendered in a 800x600 frame, even if the …
-
**Describe the bug**
I'm not sure how to supply a useful bug report here given the bizarre behaviour but - we have a large RSpec test suite including lots of headless Chrome tests that run on AWS C…
-
**Describe the bug**
Ferrum gives error on top level await calls in javascript
**To Reproduce**
Running the following javascript (through Cuprite, but the issue is in Ferrum):
```ruby
page.ex…
-
Nowdays we are using real auth service for tests, this tests should be running manually, and almost all tests must be running via mocks
-
_**Describe_ the bug**
My script crashes after a Ferrum thread throws an exception.
First I get this:
`# terminated with exception (report_on_exception is true):
C:/Users/User/.gem/ruby/3.2.0/gems…
-
**Describe the bug**
Normally, `build_exchange` is called upon `Network.requestWillBeSent`:
https://github.com/rubycdp/ferrum/blob/5ca5e9ed5e9ac8be580589e234aadc1de6929bc0/lib/ferrum/network.rb#L…
rzane updated
4 weeks ago