Hey there 馃
When I compiling my Angular Application with --prod flag,
I have this animation issue on Firefox:

Without the --prod flag it works perfectly.
I'm using:
I haven't this Bug on Chrome.
Does this happen on the previous version of FF? (57)
I noticed some weirdness with the latest version as well (although, not that particular bug).
I don't know.
Because of the Angular command "ng serve --prod":
I also noticed that the whole Website crashes,
when one of these three Animations are active:
This is the error message:
TypeError: (void 0) is not a function
It crashes on Firefox and Chrome.
Hmm the display bug is gone for some reason 馃樀
But the shift-toward animation looks different,
there are differences between --prod and without --prod 馃
Strange bugs 馃槗
TypeError: (void 0) is not a function
Which line does it occur on? (Turn off minification for prod for now?)

I need to see the line it occurs on in the unminified version.... (particularly how it relates to this library)
It occurs only at the minified version,
it occurs also very random,
so forget the list I have listed above.
The display bug occurs also randomly.
But the animation "shift-toward" for example,
looks constantly different by using --prod.
This shows the animation differences of "shift-toward" between production and no-production:
https://mnithmde-my.sharepoint.com/:f:/g/personal/thomas_gotwig_mni_thm_de/Eo7jSe5Z2qpCgrbYh_ieHLQBkR03psvy0YEARx0CpXD4ow?e=ACyMk3
It appears to be transitioning from the top-left of the document in the prod version. But I really have no idea how to fix this since it's so specific to your build
Try adding
createPopperInstanceOnInit: true
as an option?
Yeah right,
I created an small angular project which could reproduce the bug easily,
so it isn't very specific,
you can download it under the url above too,
the tooltip animations for "ng serve" and "ng serve --prod" are looking different from ground up.
Did you try that option?
Same as before,
can you reproduce it?
I can't download it right now, can later tonight
Try inspecting the HTML source to see what it's doing?
Okay good,
maybe this is an Angular CLI issue,
but I'm not really sure because I don't know what --prod exactly does 馃樀
I've downloaded your files and can reproduce it when using the --prod flag... this is really weird. Is there anything specific about the --prod flag that might cause it?
The --prod meta-flag engages the following optimization features.
Ahead-of-Time (AOT) Compilation: pre-compiles Angular component templates.
Production mode: deploys the production environment which enables production mode.
Bundling: concatenates your many application and library files into a few bundles.
Minification: removes excess whitespace, comments, and optional tokens.
Uglification: rewrites code to use short, cryptic variable and function names.
Dead code elimination: removes unreferenced modules and much unused code.
Some of these could be a problem?
EDIT: Okay yeah... Angular's minification process stuffs the library up, probably mistakenly removing code that it thinks isn't necessary but actually is 馃槗 .
I just saved the minified output file from Angular and tested in a tab, and the issue occurred, whereas unpkg's one is fine, despite being the exact same thing. I really couldn't be bothered checking what's actually different between the two, but here's a paste:
Angular (min, then prettified): https://pastebin.com/8wxtutUP
Tippy (min, then prettified): https://pastebin.com/iFFvD5QV
Solution for now, I guess, would be to use the CDN link instead of bundling it with Angular
EDIT 2: LOL! I found the issue.
It removes this line:
popper.offsetHeight
It triggers document reflow which is required for it not to transition from the top left. The minifier thinks it's unnecessary because it's not being saved as a reference, but actually is necessary... I think I can solve this issue so that minifiers don't get confused.
This _should_ be fixed in v2.1.0, but I can release a patch if it's still getting removed by the minifier... I couldn't find a way to test to make sure.
this.popper.offsetHeight
is now
function reflow(popper) {
void popper.offsetHeight
}
reflow(this.popper)
Thank you good to hear 馃馃
Most helpful comment
This _should_ be fixed in
v2.1.0, but I can release a patch if it's still getting removed by the minifier... I couldn't find a way to test to make sure.is now