Uploaded image for project: 'Nuxeo Elements'
  1. Nuxeo Elements
  2. ELEMENTS-651

nuxeo-document-suggestion does not initialize properly when bound field is not resolved

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.0
    • Fix Version/s: 2.2.7, 2.3.2
    • Component/s: Selectivity, UI

      Description

      Let's say you have a widget

          <nuxeo-document-suggestion value="{{document.properties.dc:rights}}" min-chars="0" label="Choose doc">
          </nuxeo-document-suggestion>
      

      where dc:rights is a simple String field (with no document resolver).

      The widget is supposed to be able to resolve the document by itself by issuing an extra query to fetch the document during the initSelection phase.

      However, it is not properly visually initialized and stay blanked.

      It is because the callback is called asynchronously when the widget has finished its initialization and we missed the call to

      this._selectivity.rerenderSelection();
      

      made during the synchronous init.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                1 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 4 hours
                  4h