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.
Do you want to request a feature or report a bug?
Bug.
What is the current behavior?
Angular threw an error due to misuse of transclude and transclude-slots. The generated error url linked to a not existing page. https://docs.angularjs.org/error/$compile/noslot?p0=foo&p1=bar
Note: This is not the originial generated url. I replaced the content of the query parameters p0 and p1.
What is the expected behavior?
A functional error page.
What is the motivation / use case for changing the behavior?
Helping developer.
Which versions of AngularJS, and which browser / OS are affected by this issue? Did this work in previous versions of AngularJS? Please also test with the latest stable and snapshot (https://code.angularjs.org/snapshot/) versions.
Happened on 1.5.11, I guess on every browser/OS. When you change the angular version on the plunkr to 1.6.2, it also appears.
Other information (e.g. stacktraces, related issues, suggestions how to fix)
I think its a regression bug, but I'm really not sure.
The text was updated successfully, but these errors were encountered:
ghost
changed the title
Error Page error for transclude: noSlot
Error Page for transclude: noSlot
Mar 9, 2017
Do you want to request a feature or report a bug?
Bug.
What is the current behavior?
Angular threw an error due to misuse of transclude and transclude-slots. The generated error url linked to a not existing page. https://docs.angularjs.org/error/$compile/noslot?p0=foo&p1=bar
Note: This is not the originial generated url. I replaced the content of the query parameters
p0
andp1
.If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://plnkr.co or similar (template: http://plnkr.co/edit/tpl:yBpEi4).
http://plnkr.co/edit/Sj4LpgEdzeNmKh3LThXR
What is the expected behavior?
A functional error page.
What is the motivation / use case for changing the behavior?
Helping developer.
Which versions of AngularJS, and which browser / OS are affected by this issue? Did this work in previous versions of AngularJS? Please also test with the latest stable and snapshot (https://code.angularjs.org/snapshot/) versions.
Happened on 1.5.11, I guess on every browser/OS. When you change the angular version on the plunkr to 1.6.2, it also appears.
Other information (e.g. stacktraces, related issues, suggestions how to fix)
I think its a regression bug, but I'm really not sure.
The text was updated successfully, but these errors were encountered: