Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
'Binding to event property 'onActivate' is disallowed for security reasons'
See original GitHub issueI’ve encountered this error with version ^3.2.3 and angular-cli version 3.10.10 when trying to bind the onActivate event. Don’t know what to do.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Binding to event property 'onlyCurrentMonth' is disallowed for ...
This is an issue though mostly due to Angular trying to suppress the properties starting with on*. I am monitoring this issue on...
Read more >'Binding to event property 'onActivate' is disallowed for security ...
'Binding to event property 'onActivate' is disallowed for security reasons'
Read more >Binding to event attribute 'onLabel' is disallowed for security ...
1.201705290950) I noticed a new error: Binding to event attribute 'onLabel' is disallowed for security reasons, please use (Label)=… I think ...
Read more >jest unit test error on Binding to event property 'onLabel' - Telerik
Binding to event property 'onLabel' is disallowed for security reasons, please use (Label)=... If 'onLabel' is a directive input, ...
Read more >Troubleshoot images in an Azure Compute Gallery
Creating or modifying image definitions. Error Message, Cause, Mitigation. Changing property 'galleryImage.properties.<property>' is not allowed ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The problem is not the brackets/paranthesis… Is it correct use brackets there, but the problem is the prefix
on, if you remove it should works (probably is same reserved word which break only during the test)@olastor it looks like you used brackets
[onDeactivate]instead of paranthesis(onDeactivate)to bind to outputs.