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
{{ message }}
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
I run into an ng-grid bug that makes the component behave differently in standard / ng-csp mode.
The problem lies in the fact that an expression with a trailing . evaluates to nothing when ng-csp is off and to the last property when ng-csp is on ({{foo.bar.}} is effectively the same as {{foo.bar}}).
Of course, trailing dots is something that can easily be considered illegal (throw an Error in both cases maybe).
I run into an ng-grid bug that makes the component behave differently in standard /
ng-csp
mode.The problem lies in the fact that an expression with a trailing
.
evaluates to nothing whenng-csp
is off and to the last property whenng-csp
is on ({{foo.bar.}}
is effectively the same as{{foo.bar}}
).Of course, trailing dots is something that can easily be considered illegal (throw an Error in both cases maybe).
Check out these plunkers:
ng-csp
off /ng-csp
on.The text was updated successfully, but these errors were encountered: