New issue
Advanced search Search tips

Issue 701875 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Bring traps API to Java and JS

Project Member Reported by roc...@chromium.org, Mar 15 2017

Issue description

We have a more flexible and more usable watcher API in Mojo core. This should be exposed to JS in lieu of the simple watch() cancelWatch() we have today.

This is a tracking issue for that work, including both the general-purpose core JS core API as well as the ios API facade for WebUI.
 

Comment 1 by roc...@chromium.org, May 29 2017

Cc: roc...@chromium.org
Components: Internals>Mojo
Labels: -Pri-3 Pri-2
Owner: ----
Status: Available (was: Assigned)
Project Member

Comment 2 by sheriffbot@chromium.org, May 29 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: -roc...@chromium.org rockot@google.com
Components: -Internals>Mojo Internals>Mojo>SystemsAPI
Labels: -Pri-2 -Hotlist-Recharge-Cold Pri-3
Status: Available (was: Untriaged)
Summary: Bring traps API to Java and JS (was: Bring new watcher APIs to JS)
Triage. Java and JS core APIs still reflect the old and less flexible watcher API. Should migrate to the trap API.

This is pretty low priority though because the old API is good enough for our practical purposes, and interface stability is not a concern outside of the C ABI.

Sign in to add a comment