Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

ngTransclude breaks directive execution when priority is set to -1 or lower #16411

Closed
@dknell

Description

@dknell

I'm submitting a ...

  • bug report
  • feature request
  • other

Current behavior:

As of angularjs 1.5.8, directives that transclude other directives (for example a requireAuth directive to block any events unless the user is authenticated) that have a priority of less than 0 will not fire.

Expected / new behavior:

Directives with a priority: -1 should ALWAYS fire before priority: 0 directives.

Minimal reproduction of the problem with instructions:

https://codepen.io/dknell/pen/dJjvVy

AngularJS version: 1.x.y

1.5.8

Browser: [all | Chrome XX | Firefox XX | Edge XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

all

Anything else:

This bug was introduced when terminal: true was added to ngTransclude here. Why would we want ngTransclude to block all execution of transcluded directives? This was not the case with versions 1.5.7 and below. There is no mention in the PR for why this was added.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions