Move core/dom timers to frame-specific task runners.

Move core/dom timers to frame-specific task runners.

- CSSSelectorWatch is used to implement a Blink public API that supports
  the chrome.declarativeContent [1] extension API. This is an internal
  implementation detail of Chrome, and has been moved to the unspecced
  timer task source.
- The presentation attribute [2] cache cleaner remains as-is, since it's
  a static cleaner shared among different frames.

[1] https://developer.chrome.com/extensions/declarativeContent
[2] e.g. bgcolor, topmargin, etc attributes on a body element

BUG=624694
Committed: https://crrev.com/e77aadd2660b37e28778fe0f9e423ca941b24722
Cr-Commit-Position: refs/heads/master@{#441311}

[dcheng, 2017-01-04 01:47:30]

The CQ bit was checked by dcheng@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-01-04 01:47:58]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[dcheng, 2017-01-04 01:48:44]

dcheng@chromium.org changed reviewers:
+ haraken@chromium.org

[haraken, 2017-01-04 02:13:11]

LGTM

[dcheng, 2017-01-04 02:19:17]

On 2017/01/04 02:13:11, haraken wrote:
> LGTM

Btw, do we plan on categorizing unspecced sources with more detail in the
future? Since this seems like something that won't ever be specced.

[dcheng, 2017-01-04 02:19:22]

The CQ bit was unchecked by dcheng@chromium.org

[dcheng, 2017-01-04 02:19:26]

The CQ bit was checked by dcheng@chromium.org

[commit-bot: I haz the power, 2017-01-04 02:19:31]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-01-04 03:35:26]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1483496366157230, "parent_rev":
"2c9860bf5734461735a1ac69165aae9ab726ab3a", "commit_rev":
"e30750d09e511aef0d5b7887e66fe1ddba1498fa"}

[commit-bot: I haz the power, 2017-01-04 03:35:53]

Description was changed from

==========
Move core/dom timers to frame-specific task runners.

- CSSSelectorWatch is used to implement a Blink public API that supports
  the chrome.declarativeContent [1] extension API. This is an internal
  implementation detail of Chrome, and has been moved to the unspecced
  timer task source.
- The presentation attribute [2] cache cleaner remains as-is, since it's
  a static cleaner shared among different frames.

[1] https://developer.chrome.com/extensions/declarativeContent
[2] e.g. bgcolor, topmargin, etc attributes on a body element

BUG=624694
==========

to

==========
Move core/dom timers to frame-specific task runners.

- CSSSelectorWatch is used to implement a Blink public API that supports
  the chrome.declarativeContent [1] extension API. This is an internal
  implementation detail of Chrome, and has been moved to the unspecced
  timer task source.
- The presentation attribute [2] cache cleaner remains as-is, since it's
  a static cleaner shared among different frames.

[1] https://developer.chrome.com/extensions/declarativeContent
[2] e.g. bgcolor, topmargin, etc attributes on a body element

BUG=624694

Review-Url: https://codereview.chromium.org/2614603002
==========

[commit-bot: I haz the power, 2017-01-04 03:35:54]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2017-01-04 03:39:33]

Description was changed from

==========
Move core/dom timers to frame-specific task runners.

- CSSSelectorWatch is used to implement a Blink public API that supports
  the chrome.declarativeContent [1] extension API. This is an internal
  implementation detail of Chrome, and has been moved to the unspecced
  timer task source.
- The presentation attribute [2] cache cleaner remains as-is, since it's
  a static cleaner shared among different frames.

[1] https://developer.chrome.com/extensions/declarativeContent
[2] e.g. bgcolor, topmargin, etc attributes on a body element

BUG=624694

Review-Url: https://codereview.chromium.org/2614603002
==========

to

==========
Move core/dom timers to frame-specific task runners.

- CSSSelectorWatch is used to implement a Blink public API that supports
  the chrome.declarativeContent [1] extension API. This is an internal
  implementation detail of Chrome, and has been moved to the unspecced
  timer task source.
- The presentation attribute [2] cache cleaner remains as-is, since it's
  a static cleaner shared among different frames.

[1] https://developer.chrome.com/extensions/declarativeContent
[2] e.g. bgcolor, topmargin, etc attributes on a body element

BUG=624694

Committed: https://crrev.com/e77aadd2660b37e28778fe0f9e423ca941b24722
Cr-Commit-Position: refs/heads/master@{#441311}
==========

[commit-bot: I haz the power, 2017-01-04 03:39:33]

Patchset 1 (id:??) landed as
https://crrev.com/e77aadd2660b37e28778fe0f9e423ca941b24722
Cr-Commit-Position: refs/heads/master@{#441311}

[haraken, 2017-01-04 11:44:09]

On 2017/01/04 02:19:17, dcheng wrote:
> On 2017/01/04 02:13:11, haraken wrote:
> > LGTM
> 
> Btw, do we plan on categorizing unspecced sources with more detail in the
> future? Since this seems like something that won't ever be specced.

Not really. We have UnspecedTimer and UnspecedLoading. That's it.

"Unspeced" means a task not defined in the spec (i.e., an internal task in
Blink). It doesn't mean a task that is defined in the spec but is not yet
associated with any task source. There's a discussion to introduce
"PlatformAPITask" to distinct between the two.