Adding property/event bindings to ng-content should error #24259

Activity

1. vicb

   changed the title [-]Adding unsupported attributes to ng-content should error[/-] [+]Adding property/event bindings to ng-content should error[/+] on Jun 1, 2018
2. vicb commented on Jun 1, 2018

   

   vicb

   on Jun 1, 2018

   Contributor

   More actions

   Adding an attribute could be used for re-projection: <ng-content selector="a[title]" someRandomName></ng-content> and then <ng-content selector="[someRandomName]"></ng-content>
3. vicb

   added

   type: bug/fix

   freq1: low

   severity1: confusing

   area: coreIssues related to the framework runtimeIssues related to the framework runtime

   on Jun 1, 2018
4. ngbot

   added this to the Backlog milestone on Jun 1, 2018
5. vicb

   modified the milestones: Backlog, Ivy on Jun 1, 2018
6. pkozlowski-opensource

   added

   hotlist: error messages

   on Feb 10, 2019
7. pkozlowski-opensource

   added

   core: content projection

   on Mar 14, 2020
8. pkozlowski-opensource

   added

   state: confirmed

   triage #1

   design complexity: low-hanging

   on May 25, 2020
9. jelbourn

   removed

   severity1: confusing

   on Oct 1, 2020
10. AndrewKushnir

    removed

    triage #1

    on Mar 15, 2022
11. toha-marko

    added a commit that references this issue on May 13, 2026

    fix(compiler): report error for property/event bindings on ng-content

    ...

    This issue will close once commit f825e73 is merged into the 'main' branch.

    f825e73
12. JeanMeche commented on Aug 16, 2026

    

    JeanMeche

    on Aug 16, 2026

    Member

    More actions

    Closing as we've suggested this could be handled by a linting rule: #68910
13. JeanMeche

    closed this as not plannedon Aug 16, 2026
14. angular-automatic-lock-bot commented on Oct 20, 2026

    

    angular-automatic-lock-botBot

    on Oct 20, 2026

    More actions

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    _{This action has been performed automatically by a bot.}
15. angular-automatic-lock-bot

    locked and limited conversation to collaborators on Oct 20, 2026