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
I think that the p:option in this test is missing static="true". Otherwise, I think it needs the eager-eval feature flag. Or I'm confused about how this test is substantially different from ab-option-064 where an error is not raised.
I think the same is true of ab-option-027.
The text was updated successfully, but these errors were encountered:
026 needs eager-evaluation: The XPath expression for the option is invalid, but option is never used.
027 Not sure about that: Here the XPath expression for the default value is invalid, but a value is provided on the call. Can we simply ignore the error in the default expression?
Yes, 064 is marked eager. I was only pointing out that I think 026 is the same situation as 064. Sounds like you agree.
For 027, if you're doing lazy evaluation, I certainly can't think of any reason why you'd attempt to evaluate the default if a value has been provided.
I think that the
p:option
in this test is missingstatic="true"
. Otherwise, I think it needs theeager-eval
feature flag. Or I'm confused about how this test is substantially different fromab-option-064
where an error is not raised.I think the same is true of
ab-option-027
.The text was updated successfully, but these errors were encountered: