This repository was archived by the owner on Apr 12, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
preLink, DOM manipulation ... compositeLinkFn "TypeError: Cannot read property 'childNodes' of undefined" #2532
Description
Activity
Update: Seems like, I would do the DOM manipulation (including removing children) in the compile function.
Please confirm and close the bug.
Thanks
PrashantUpdate 2: I cannot manipulate the DOM or child DOM if transclude = true. I still think, the directive should be able to manipulate the DOM before the link/compile phase.
As part of our effort to clean out old issues, this issue is being automatically closed since it has been inactivite for over two months.
Please try the newest versions of Angular (
1.0.8and1.2.0-rc.1), and if the issue persists, comment below so we can discuss it.Thanks!
In one of my directives, in the preLink function I manipulate the DOM (element itself) and its children and descendants.
Later, in the compositeLinkFn, I get the above error.
I also noticed, that if I do the same thing (remove children) in the postLinkFn, I get no errors.
Question: Is this by design (not be able to remove the children in the preLink) or is this a bug. I thought, preLink was supposed to let you manipulate the DOM any way you want.
Is there a way, I can do whatever I want with the DOM before the real compile starts. Something like a preCompile which starts from parent. OR I think there should be a capturePhase compile which goes top-down. In this phase, the compiler would have no knowledge of any descendants and the DOM can be easily manipulated.