<p dir="auto">FontUtils <a href="http://threejs.org/docs/#Reference/Extras/FontUtils" rel="nofollow">http://threejs.org/docs/#Reference/Extras/FontUtils</a><br>
when you try to click over source, there's a dead link.</p>
<p dir="auto">I've been looking at contributing documentation changes and noticed that there are some inconsistencies with the return value of methods.</p>
<p dir="auto">For example, <a href="http://threejs.org/docs/#Reference/Math/Vector3" rel="nofollow">Vector3's page</a> has a <code class="notranslate">this</code> after all methods that modify the <code class="notranslate">Vector3</code> in place and then return the same <code class="notranslate">Vector3</code>. But there are methods like <a href="http://threejs.org/docs/#Reference/Math/Vector3.distanceToSquared" rel="nofollow"><code class="notranslate">.distanceToSquared()</code></a> that have no return value after the method.</p>
<p dir="auto">So my questions are:</p>
<ol dir="auto">
<li>When should a return value follow a method definition?</li>
<li>When should that return value text be <code class="notranslate">this</code> or the type, eg. <code class="notranslate">Vector3</code>?</li>
</ol>
<p dir="auto"><em>Side Note:</em> There are methods that link to non-existent pages because their return type is a standard JS type ( eg. Boolean, Float, etc ). This is confusing if you are expecting to be redirected to the page on that type.</p>