[Bug 25537] Expose expiration information to the application

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25537

--- Comment #4 from David Dorwin <ddorwin@google.com> ---
I thought about adding an event, but the use cases seem limited and I didn't
want to add more complexity until we're sure we need it.

It's not something that is expected to change frequently. For the update()
scenario, the promise should be resolved after any related updates are applied.
(For the moments) when applications care about other scenarios, it seems
polling should work and precise updates are not necessary (as they might be for
a change in usable keys)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 6 May 2014 21:21:33 UTC