Issue metadata
Sign in to add a comment
|
Component Request for Blink>Lifecycle |
||||||||||||||||||||||
Issue description1] Component Name: Blink > Lifecycle Guideline 1 (Clarity): Component name should be descriptive beyond the core project team (i.e. please avoid using non-industry standard abbreviations, code words, project names, etc...) Guideline 2 (Permanence): Component names should describe features/ functions and not team names, code locations, etc..., which are more subject to change and make the hierarchy less predictable for people triaging issues. Guideline 3 (Specific): Components are meant to explicitly track functional work areas. If you are trying to track a Proj(ect) or an on-going effort (e.g. Hotlist-Conops), please instead request a label for a (Proj- or Hotlist-) Guideline 4 (Discoverable/ Predictable): Components should be parented where people would logically expect to find them (i.e. follow product decomposition when naming versus team decomposition) 2] Parent Component (e.g. Blink, UI>Browser, etc...): _____ Note: We generally avoid creating new component namespaces, unless there is a new hierarchy that needs to be expressed. Please try and use existing components as parents. 3] Description of Component: We are formalizing the lifecycle of web apps with the goals of improving the end user experience, providing APIs to enable developers to build optimal web experiences and developing the right incentive structure for efficient resource usage by web apps. Existing lifecycle events include pagevisibility, beforeunload, unload, pagehide, pageshow. We will add new, consolidated lifecycle signals. 4] Admin/ Owner: panicker@chromium.org 5] nduca@'s team on a weekly basis.
,
Jun 27 2017
Yes, I did mean that this component will cover pagevisibility etc. What is your suggestion instead? Blink>HTML>Lifecycle or something else? For background for this work see these docs: https://docs.google.com/presentation/d/1uhj0Hs5U7tXBrmEMYddcPHtYyBky7lpV-B-YjsrjIKo/edit#slide=id.p https://docs.google.com/document/d/1UuS6ff4Fd4igZgL50LDS8MeROVrOfkN13RbiP2nTT9I/edit
,
Jun 28 2017
If you'll make a new specification like "Lifecycle specification", Blink>Lifecycle or Blink>PerformanceAPIs>Lifecycle would be reasonable. If the HTML specification continues to have beforeunload, unload, pagehide, and pageshow events, adding Blink>HTML>Lifecycle too would help you.
,
Jul 12 2017
,
Jul 12 2017
There will be a new spec that links to relevant parts of HTML spec. So Blink>Lifecycle makes sense to me. (Later if needed we can add Blink>HTML>Lifecycle) I am not sure why you are suggesting Blink>PerformanceAPIs>Lifecycle -- as this is not really a performance API.
,
Aug 7 2017
Is this resolved? +ojan, to see if he has opinions on one of these component names as well.
,
Aug 7 2017
I think Blink>Lifecycle is ok.
,
Sep 7 2017
Blink>Lifecycle strikes me as ambiguous. To be more explicit, could we make this Blink>PageLifecycle or Blink>PageEvents or Blink>Events or Blink>Events>PageState?
,
Sep 11 2017
Blink>PageLifecycle sounds reasonable to me. "Events" is too specific IMO, as lifecycle involves lifecycle STATES and events that fire on certain STATE transitions.
,
Sep 11 2017
,
Sep 14 2017
Friendly ping, what's the next step here?
,
Sep 22 2017
This has been created, but the bug is still open. Closing now. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by tkent@chromium.org
, Jun 27 2017