Skip to content

Latest commit

 

History

History
37 lines (27 loc) · 2.45 KB

FAQ.md

File metadata and controls

37 lines (27 loc) · 2.45 KB
Raw

Frequently Asked Questions

  1. How can I file a bug report: Please don't hesitate to let us know if you find something wrong! In general we are going to ask for an example of the problem failing, which can be as simple as a jsfiddle/jsbin/etc. We've put together a jsfiddle template to ease this. (We will keep this link up to date as new releases occur, so feel free to check back here)

  2. Why is it slower when compiling? The Handlebars compiler must parse the template and construct a JavaScript program which can then be run. Under some environments such as older mobile devices this can have a performance impact which can be avoided by precompiling. Generally it's recommended that precompilation and the runtime library be used on all clients.

  3. Why doesn't this work with Content Security Policy restrictions? Handlebars generates a dynamic function for each template which can cause issues with pages that have enabled Content Policy. It's recommended that templates are precompiled or the unsafe-eval policy is enabled for sites that must generate dynamic templates at runtime.

  4. How can I include script tags in my template? If loading the template via an inlined <script type="text/x-handlebars"> tag then you may need to break up the script tag with an empty comment to avoid browser parser errors:

<script type="text/x-handlebars">
  foo
  <scr{{!}}ipt src="bar"></scr{{!}}ipt>
</script>

It's generally recommended that templates are served through external, precompiled, files, which do not suffer from this issue.

  1. Why are my precompiled scripts throwing exceptions? When using the precompiler, it's important that a supporting version of the Handlebars runtime be loaded on the target page. In version 1.x there were rudimentary checks to compare the version but these did not always work. This is fixed under 2.x but the version checking does not work between these two versions. If you see unexpected errors such as undefined is not a function or similar, please verify that the same version is being used for both the precompiler and the client. This can be checked via:
handlebars --version

If using the integrated precompiler and

console.log(Handlebars.VERSION);

On the client side.

Should these match, please file an issue with us, per our issue filing guidelines.