Skip to content

Use of possibly undefined variables in Context Processing #372

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

Closed
kasei opened this issue Feb 14, 2020 · 2 comments · Fixed by #377
Closed

Use of possibly undefined variables in Context Processing #372

kasei opened this issue Feb 14, 2020 · 2 comments · Fixed by #377

Comments

@kasei
Copy link
Contributor

kasei commented Feb 14, 2020

(Related to #265, #356)

Context Processing step 5.2.5 uses loaded context which is only defined in 5.2.4.3 (which is not necessarily evaluated prior to 5.2.5)

Context Processing step 5.2.5 uses context document which is only defined in 5.2.4 (which is not necessarily evaluated prior to 5.2.5)

gkellogg added a commit that referenced this issue Feb 15, 2020
… that the previous document was cached in 5.2.3 of the Create Context Algorithm.

Fixes #372.
@gkellogg
Copy link
Member

Updated in #377.

@gkellogg gkellogg self-assigned this Feb 16, 2020
@kasei
Copy link
Contributor Author

kasei commented Feb 17, 2020

@gkellogg new language in #377 looks good for this. Thanks.

gkellogg added a commit that referenced this issue Feb 18, 2020
… that the previous document was cached in 5.2.3 of the Create Context Algorithm.

Fixes #372.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants