You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By the proposed Conditional Syntax [Design Doc], conditions could be recursive (i.e. nested). For example, we can specify and conditions as elements of an or condition.
However, since allowing infinite nests may cause some problems in implementations, each browser will restrict the depth of nests and it will involve inconsistent behaviors between browsers.
I suggest having max recursion limits in the specification to avoid such confusion.
The text was updated successfully, but these errors were encountered:
I agree to have maximum recursion limit. Do we also have a limit to conditions listed in or and and? I mean that or and and can take a list, and writing too long list can also be harmful.
By the proposed Conditional Syntax [Design Doc], conditions could be recursive (i.e. nested). For example, we can specify
and
conditions as elements of anor
condition.However, since allowing infinite nests may cause some problems in implementations, each browser will restrict the depth of nests and it will involve inconsistent behaviors between browsers.
I suggest having max recursion limits in the specification to avoid such confusion.
The text was updated successfully, but these errors were encountered: