-
-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
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
compatibility with Emulation.setVirtualTimePolicy #264
Comments
Could you attach FERRUM_DEBUG logs as well? |
There's no |
yup, it does appear https://gist.github.com/dreyks/9826a7a42277798606056daa5b135121 |
Sorry, this convo slipped thru the cracks. I'm afraid it's Chrome's issue then. We should raise an issue like this one https://issues.chromium.org/issues/40923369 though fix is not going to happen quick. Could you please create one? |
so is the issue in that chrome doesn't send |
@dreyks yes exactly |
ok, thx, I'll do that. let's keep the issue open, I'll post the link to a ticket when i make one |
I linked wrong issue, the updated comment has a link on a better one with better explanation. Bad thing is that it takes them forever to fix anything, so don't expect any real quick fix :( |
I'm trying to mock time on the frontend, for this I'm mocking time on the backend using ActiveSupport's travel_to and then trying to make it propagate to the browser
this does work returning
Mon Jan 01 2024 00:00:00
but then i get an errorlooks like something doesn't work well with virtual time
according to the docs
policy: 'pause'
means that browser is not allowed to fast-forward the time when it's out of workif i pass
policy: 'advance'
ferrum doesn't complain but the time advances too quickly: onevisit
and it's already the next monthany ideas?
The text was updated successfully, but these errors were encountered: