[css-layout-api] Add a bunch of TODO issues.

Author: bfgeek

css-layout-api/Overview.bs

@@ -43,15 +43,6 @@ urlPrefix: https://tc39.github.io/ecma262/#sec-; type: dfn;
         text: TypeError
 </pre>
 
-<!--
-TODO
- - Fix layout invalidation section.
- - Fix examples.
- - Add utility functions.
- - Define invalid fragment.
- - Layout instance on box is incorrect.
--->
-
 Introduction {#intro}
 =====================
 
@@ -78,7 +69,6 @@ Layout API Containers {#layout-api-containers}
         This value causes an element to generate an inline-level <a>layout API container</a> box.
 </dl>
 
-
 A <dfn>layout API container</dfn> is the box generated by an element with a computed 'display' of
 ''layout()'' or ''inline-layout()''.
 
@@ -112,12 +102,15 @@ A <a>layout API container</a> has a <dfn>layout instance</dfn>, initially this i
 is an instance of the author defined layout class (see [[#registering-layout]]). If the <a>box</a>'s
 <a>computed value</a> of 'display' changes, this must be reset to null.
 
+Issue: Having the layout instance on the box is wrong, should really be a map on the layout worklet
+    global scope.
+
 Layout API Container Painting {#painting}
 -----------------------------------------
 
 <a>Layout API Container</a> children paint exactly the same as inline blocks [[!CSS21]], except that
 the order in which they are returned from the layout method (via
-{{FragmentResultOptions/childFragments}} is used in place of raw document order, and 'z-index'
+{{FragmentResultOptions/childFragments}}) is used in place of raw document order, and 'z-index'
 values other than ''z-index/auto'' create a stacking context even if 'position' is ''static''.
 
 Layout API Model and Terminology {#layout-api-model-and-terminology}
@@ -515,7 +508,7 @@ dictionary BreakTokenOptions {
 enum BreakType { "none", "inline", "inline-hyphen", "column", "page", "region" };
 </pre>
 
-Issue(w3c/css-houdini-drafts#258): What type of {{BreakType}}s are needed?
+Issue: Fill out other inline type break types.
 
 A {{LayoutChild}} can produce multiple {{Fragment}}s. A {{BoxLayoutChild}} may fragment in the block
 direction if a {{ConstraintSpace/blockFragmentation}} is not none. A {{InlineLayoutChild}} may
@@ -525,6 +518,8 @@ A subsequent {{Fragment}} is produced by using the previous {{Fragment}}'s {{Fra
 This tells the <a>child layout</a> to produce a {{Fragment}} starting at the point encoded in the
 {{ChildBreakToken}}.
 
+Issue: Explain resuming the author defined layout.
+
 <div class="example">
 This example shows a simple inline layout which places child fragments in the inline direction. It
 places each of its on a line, aligning their dominant baselines.
@@ -717,6 +712,12 @@ partial interface LayoutWorkletGlobalScope {
     LayoutSize resolveScrollbarSize(ConstraintSpace constraintSpace,
                                     StylePropertyMapReadOnly styleMap);
 };
+
+[Exposed=LayoutWorklet]
+interface Layout {
+    readonly attribute sequence&lt;DOMString> inputProperties;
+    readonly attribute sequence&lt;DOMString> childInputProperties;
+};
 </pre>
 
 Issue: Specify the behaviour of these functions.
@@ -736,6 +737,8 @@ name to child input properties map</dfn>. Initialy these maps are empty and are
 Each <a>box</a> has an associated <dfn>layout valid flag</dfn>. It may be either
 <dfn>layout-valid</dfn> or <dfn>layout-invalid</dfn>. It is initially set to <a>layout-invalid</a>.
 
+Issue: The above flag is too restrictive on user agents, change.
+
 When the <a>computed style</a> for a |box| changes, the user agent must run the following steps:
     1. Let |layoutFunction| be the <<layout()>> or <<inline-layout()>> function of the 'display'
         property on the <a>computed style</a> for the |box| if it exists. If it is a different type
@@ -923,8 +926,6 @@ layout engine may run the algorithm asynchronously with other work, and/or on a
 execution. When {{Fragment}}(s) have been produced by the engine, the user-agent will 'tick' the
 generator object with the resulting {{Fragment}}(s).
 
-Issue: Write algorithm "<dfn>generate a fragment</dfn>" which encapsulates this.
-
 <div class="example">
 An example layout engine written in javascript is shown below.
 
@@ -990,6 +991,11 @@ dictionary FragmentResultOptions {
 };
 </pre>
 
+Issue: Specify how we do min/max content contributions.
+
+Issue: Need to specify that the {{LayoutChild}} objects should remain the same between layouts so
+    the author can store information? Not sure.
+
 When the user agent wants to <dfn>generate a layout API fragment</dfn> of a <a>layout API formatting
 context</a> for a given |box|, |constraintSpace|, |children| and an optional |breakToken| it
 <em>must</em> run the following steps:
@@ -1026,6 +1032,8 @@ context</a> for a given |box|, |constraintSpace|, |children| and an optional |br
         If |definition| does not exist, let the fragment output be an <a>invalid fragment</a> and
         abort all these steps.
 
+        Issue: Define what an "invalid fragment" is.
+
     6. Let |layoutInstance| be the result of looking up the <a>layout instance</a> on the |box|. If
         |layoutInstance| is null run the following substeps.