jsf.js_next_gen 4.0.0-beta-8 → 4.0.0-beta-9

package/dist/docs/variables/faces.separatorchar.html

@@ -14,7 +14,7 @@
 <li><a href="../modules/faces.html">faces</a></li>
 <li><a href="faces.separatorchar.html">separatorchar</a></li></ul>
 <h1>Variable separatorchar</h1></div>
-<div class="tsd-signature">separatorchar<span class="tsd-signature-symbol">:</span> <span class="tsd-signature-type">any</span><span class="tsd-signature-symbol"> = ...</span></div>
+<div class="tsd-signature">separatorchar<span class="tsd-signature-symbol">:</span> <span class="tsd-signature-type">string</span><span class="tsd-signature-symbol"> = ...</span></div>
 <div class="tsd-comment tsd-typography"><p>SeparatorChar as defined by facesContext.getNamingContainerSeparatorChar()</p>
 </div></div>
 <div class="col-4 col-menu menu-sticky-wrap menu-highlight">

package/dist/window/faces-development.js

@@ -3465,7 +3465,9 @@ var faces;
     function getSeparatorChar() {
         const sep = '#{facesContext.namingContainerSeparatorChar}';
         //We now enable standalone mode, the separator char was not mapped we make a fallback to 2.3 behavior
-        return (faces.separatorchar.indexOf(/\#\{/gi) != -1) ? AjaxImpl_1.Implementation.getSeparatorChar() : sep;
+        //the idea is that the separator char is provided from the underlying container, but if not then we
+        //will perform a fallback (aka 2.3 has the url fallback behavior)
+        return (sep.match(/\#\{facesContext.namingContainerSeparatorChar\}/gi)) ? AjaxImpl_1.Implementation.getSeparatorChar() : sep;
     }
     let ajax;
     (function (ajax) {