A background operation is the ability for an origin to execute potentially resource consuming code in the background.
I think the definition should explain what a background operation is and maybe list some examples. This feels like it's instead defining a background operation budget. Specifically I don't think a background action is an ability but it's a concrete action where as a budget would measure the ability to perform actions.
I found it difficult to understand the spec the first time around because this definition is the underpinning of the specification but it doesn't really explain what a background operation is. I was wondering if we were including any events (input, timeout, request animation frames) and if they were measure by count, cpu time, wall time.
Currently it says:
I think the definition should explain what a background operation is and maybe list some examples. This feels like it's instead defining a background operation budget. Specifically I don't think a background action is an ability but it's a concrete action where as a budget would measure the ability to perform actions.
I found it difficult to understand the spec the first time around because this definition is the underpinning of the specification but it doesn't really explain what a background operation is. I was wondering if we were including any events (input, timeout, request animation frames) and if they were measure by count, cpu time, wall time.