In v1.1.4 minified, the container option is broken, as you can see in this linked JSBin. Even though the container is specified to be the <body>, Awesomplete wraps the input in a <div>. Upon inspecting the minified source code, we can see that the minifier has inlined the _.CONTAINER(...) method call into the Awesomplete constructor, and therefore, the container callback provided in the options object is never called.
If you remove the .min from the <script> tag, loading in the non-minified version of Awesomplete, the container option works as expected, and we can see that Awesomplete does not wrap the <input> in a <div>, and instead leaves it directly in the <body>.
In v1.1.4 minified, the
containeroption is broken, as you can see in this linked JSBin. Even though the container is specified to be the<body>, Awesomplete wraps the input in a<div>. Upon inspecting the minified source code, we can see that the minifier has inlined the_.CONTAINER(...)method call into the Awesomplete constructor, and therefore, thecontainercallback provided in the options object is never called.If you remove the
.minfrom the<script>tag, loading in the non-minified version of Awesomplete, thecontaineroption works as expected, and we can see that Awesomplete does not wrap the<input>in a<div>, and instead leaves it directly in the<body>.