New issue
Advanced search Search tips

Issue 875203 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Running idle tasks from browser tests

Project Member Reported by rakina@chromium.org, Aug 17

Issue description

There's currently no way for browser tests to ask the renderer to run idle tasks immediately (for testing).

We encountered this when trying to make Find-in-page use idle tasks, and we had to add a flag in the Find-in-page mojo call from browser to renderer to solve this (see crrev.com/c/1152710).

 
Just to make sure — now the idle tasks are running eventually, correct (I'm asking because we have a problem when they don't run at all in layout tests).

We have runIdleTasks in js bindings for layout tests. I wonder if it would help to support it in browser tests as well? 
> Just to make sure — now the idle tasks are running eventually, correct (I'm asking because we have a problem when they don't run at all in layout tests).

Do you mean when I'm not forcing the runs? No, I don't think they do (or at least, not fast enough because all the test for Find-in-page timed out both the ones on blink or browser)

> We have runIdleTasks in js bindings for layout tests. I wonder if it would help to support it in browser tests as well? 

Yeah, being able to force the running of idle tasks from browser side is ideal. From hajimehoshi@, I guess this is the first occurence of the use case, so I understand if it's not high priority.

Sign in to add a comment