Uploaded image for project: 'Fluid Infusion'
  1. Fluid Infusion
  2. FLUID-4261

"Tag Singularity Problem" prevents expression of some component trees, especially in recursive cases



    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.4, 1.5
    • Fix Version/s: None
    • Labels:


      A recent valiant attempt to refactor the UIOptions table of contents control to become fully declarative ran into a (very) long-standing renderer issue, the "tag singularity problem". In its current form, the renderer is unable to abstract over the difference between the cases where two cutpoints (as they now are) match two different markup nodes, and when they match the same one. Support has been provided for the "tag elision syntax" where a markup node whose renderer component had an ID beginning with the tilde character ~ would be elided from the finally rendered markup - however, this is somewhat cumbersome and still can't cover all the cases where singularity arises.
      This version of TableOfContents.js https://github.com/jobara/infusion/blob/fb9a364e4b5640ed667cc47cdbb1e76c28e11fc5/src/webapp/components/tableOfContents/js/TableOfContents.js part of a branch for FLUID-4209, contains a "moral implementation" which should be possible to be supported. However, under the current system, the recursive call to "fluid.tableOfContents.level" fails - the markup appearing as follows:

      <ul class="flc-tocLevel-headingLevel">
      <li class="flc-tocLevel-headingContainer">
      <a class="flc-tocLevel-headingText"></a>

      The intended effect is that a fresh instance of "level" can appear nested immediately after the "headingText" link, nested within the "headingContainer". Even with the "tag elision syntax" (which would require, for a start, some corruption of the markup with an unnecessary tag) this cannot be supported - since in this non-one-pass rendering case, the elided placeholder container could not then be the target of a decorator issued against the markup.

      The best plan is to try to add explicit workflow for cases like these as part of the "Renderer antigens" work FLUID-4260, rather than complicate the core workflow of the renderer any further.


          Issue Links



              antranig Antranig Basman
              antranig Antranig Basman
              0 Vote for this issue
              0 Start watching this issue