New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Copy edits for all remaining parts #687
Conversation
|
||
As suggested by others in the past discussions, we propose to use nested templates for these cases: | ||
As suggested by others in past discussions,fo these cases we propose to use nested templates: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happened here?
@@ -338,7 +338,7 @@ To make this process more streamlined, we propose treating inner template elemen | |||
}; | |||
``` | |||
|
|||
With this interface, the template process callback that implements foreach and other kinds of looping constructs could simply call `replace` with newly constructed elements as follows: | |||
With this interface, the template process callback that implements a *foreach* and other kinds of looping constructs could simply be called `replace` with newly constructed elements, as follows: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The original sentence was correct. "The template process callback ~ could simply call replace
with newly constructed elements,".
|
||
We like the idea of supporting very basic control flow such as `if` and `foreach` in the default template process callback but we don't think it's a show stopper if the default template process callback didn't support them in the initial cut. | ||
|
||
We like the idea of supporting very a basic control flow such as `if` and `foreach` in the default template process callback, but we don't think it'd be a show stopper if the default template process callback didn't support them in the initial cut. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should have said "supporting very basic control flow statements".
5. For every [descendant](https://dom.spec.whatwg.org/#concept-tree-descendant) node *currentNode* of *instance* in [tree order](https://dom.spec.whatwg.org/#concept-tree-order), run these steps: | ||
1. If *currentNode* is a [`template` element](https://html.spec.whatwg.org/multipage/scripting.html#the-template-element): | ||
1. Run the concept to _adjust single node case_ with *currentNode*. | ||
2. Let *nodeValueSetter* be a new instance of the _node value setter_ with *currentNode*, the [previous sibling](https://dom.spec.whatwg.org/#concept-tree-next-sibling) of *currentNode*, the [next sibling](https://dom.spec.whatwg.org/#concept-tree-next-sibling) of *currentNode*, an empty _previous replacement nodes_, _fully templatized_ flag set to the result of running the concept to _determine full templatizability_ with *currentNode*, and an empty _node template part list_. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm using _ to only refer to variable names. So please don't italicize concepts defined elsewhere.
5. [Remove](https://dom.spec.whatwg.org/#concept-node-remove) *currentNode* from the *currentNode*'s [parent](https://dom.spec.whatwg.org/#concept-tree-parent). | ||
6. Run the concept to _apply node template part list_ with *nodeValueSetter*. | ||
5. For every [descendant](https://dom.spec.whatwg.org/#concept-tree-descendant) node *currentNode* of *instance* in [tree order](https://dom.spec.whatwg.org/#concept-tree-order), run these steps: | ||
1. If *currentNode* is a [`template` element](https://html.spec.whatwg.org/multipage/scripting.html#the-template-element): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to keep using 4-space indentations. Please revert.
No description provided.