After re-factoring in v1.9.32 the following code is generated the error: const creator = new SurveyCreator.SurveyCreator({ showPropertyGrid: false });

We do not update internal models in some React Components on changing props. It can lead to incorrect behavior.

Preview tab hides start page and do not allow to show it. It should work with the start page as with any other pages in the Preview tab.

After re-factoring in v1.9.32 the following code is generated the error: const creator = new SurveyCreator.SurveyCreator({ showSidebar: false });

Are you requesting a feature, reporting a bug or asking a question?

Question

What is the current behavior?

No official React 18 support

What is the expected behavior?

Official React 18 support

How would you reproduce the current behavior (if this is a bug)?

Install with React 18

I couldn't find a ticket on official React 18 support so thought it would be nice for the community to have some visibility on this.

Right now it is impossible to have two surveys on English and Spanish on the same page. It brings issues in SurveyJS Creator V2, since we can have Property Grid in English (using our survey) and survey on designer surface in Spanish. As result, it starts work incorrectly and survey on designer surface may show incorrect locale strings.

Chaning "renderAs" property for matrixdropdown column doesn't apply immediately for a template question. As result, since this property is dynamic and based on cellType, it leads to incorrect behavior in the property grid in Creator V2.

If there are errors in matrix dynamic (matrix cell question) or in panel dynamic (in question inside the panel) then panel/page "focusFirstErrorQuestion" function doesn't work.

There is no way to apply a different css style for a different composite questions using global css. For example, if you have a composite question: "customerinfo" you should set it's style as: survey.css["customerinfo"] = { mainRoot: "customercss" };. It works for all other questions.

We have getType() function that returns the object type. Sometimes you need to know if the object instance is inherited from another object. For example, is the question "dropdown" or inherited from "dropdown". In this case obj.getType() === "dropdown" will not work and it should be used obj.isDescendantOf("dropdown"); in this case.

If there are several questions in one line, then trying to insert a new question between these questions and a question with a new line generates incorrect result.

For instance, the following screencast shows a numeric nps_score question that doesn't accept contains and some other operations. It makes sense because these operations are valid only for string question, but in this case why are they on the list? We need to filter the drop-down values.

https://www.screencast.com/t/vXoQM4qe

Steps to reproduce:

1. Set survey locale to non-default locale via property grid
2. Add boolean question: on this step Yes/No labels are localised correctly
3. Click on Preview Tab
4. Click on Designer Tab
5. boolean localised labels are reset to labels with default Yes/No

In-line editing of (for instance) question titles or choices does not work in Safari (running safari version 14.1.1).

If a developer reset/change the existing survey when translation tab is opening then filter by page action should be set to "All pages".

We do not have the easy way to change the default question JSON when a user creates a new question on designer. It should be as easy as:

SurveyCreatorCore.settings.toolbox.defaultJSON["image"] = 
  { imageLink : "https://www.rd.com/wp-content/uploads/2021/04/GettyImages-141809950.jpg" };

We should use isDescendantOf() function instead of getType() function for getting correct component wrapper name. Otherwise new questions types inherited from our standard questions will not work correctly in Creator V2.

Hello SurveyJS team,

the survey tabulator does not escape script tags correcltly.

I have taken the the survey tabulator example and added a HTML button with a onclick handler on it and it executes. This is a security issue and should not be the case. https://plnkr.co/edit/J99S1lklsPL6d27J

The survey editor and survey display component escape this correctly.

Best Johannes

Now:

var surveyResultNode = document.getElementById("surveyDashboard");
surveyResultNode.innerHTML = "";
visPanel.render(surveyResultNode);

Suggestion:

visPanel.render("surveyDashboard");

Some users request column title different form column title: e.g. if they are using markdown.

See the https://surveyjs.answerdesk.io/ticket/details/t9444/markdown-matrix-tooltip-on-matrix-cells-is-broken-shows-the-html-values thread for more deatils

Demo: https://surveyjs.io/Examples/Survey-Creator?id=real-nps&platform=ReactjsV2&theme=defaultV2

Screencapture: https://www.screencast.com/t/EvC4xfcz

refered to https://github.com/surveyjs/service/issues/222

we need to revert https://github.com/surveyjs/survey-creator/issues/2456

If there are several questions inside a panel and user select the panel then after clicking "Add new Question" on Panel footer, a new question can be added in the middle of other questions.

We do not have an event, that fires after property grid survey is setup. Here the event declaration:
  /**
   * The event is called after a survey that represents the Property Grid is created and all its questions (property editors) are setup.
   * You can use this event to modify this survey to change the property grid behavior
   * <br/> options.obj the survey object that is currently editing in the property grid
   * <br/> options.survey the property grid survey
   */
   public onPropertyGridSurveyCreated: Survey.Event<(sender: CreatorBase, options: any) => any, any>

Developer can use onModified event to find that property has been changed. It is better to have it's own event since it used a lot.

  /**
   * The event is fired when a property in any survey object object is changed.
   * <br/> sender the survey creator object that fires the event
   * <br/> options.obj the survey object which property has been changed.
   * <br/> options.propertyName  the name of the changed property.
   * <br/> options.value the property value.
   * @see onPropertyValidationCustomError
   * @see onPropertyValueChanging
   */
   public onSurveyPropertyValueChanged: Survey.Event< (sender: CreatorBase, options: any) => any, any>

If a panel dynamic has dropdowns with "others"/"comments" values, adding new panel with several existing panels is extremely slow.

It is hard to find an autogenerated page by name for "survey.questionsOnPageMode" property equals to "questionOnPage". It is better to set the same name as a question name.

The following survey doesn't work correctly. It shows erros on complete/next page, instead of on value changed.

{
   "elements": [
    {
     "type": "text",
     "name": "question1",
     "inputType": "number",
     "min": 1,
     "max": 4
    }
 ],
 "checkErrorsMode": "onValueChanged"
}

The following JSON doesn't work correctly:

{
    elements: [
      { type: "boolean", name: "q1", defaultValueExpression: "true" },
    ],
  }

Question should have "true" value, but it has "false".

If dynamic panel has a "renderMode" value different from "list", display one panel at a time, then we do not allow to go to another panel if there is an error on the current. However we allow to add a new panel, which is inconsistent. We have to show errors and do not allow to add a new panel if there are errors on the current panel.

The following code doesn't work correctly. The "q2" value is "other", instead of "item2".

  const survey = new SurveyModel({
    elements: [
      {
        type: "checkbox",
        name: "q1",
        choices: ["apple", "banana", "orange"],
      },
      {
        type: "radiogroup",
        name: "q2",
        choices: [
          "item1",
          {
            value: "item2",
            visibleIf: "{q1} = ['apple']",
          },
          "item3",
        ],
        hasOther: true,
      },
    ],
  });
  survey.data = {
    q2: "item2",
    q1: ["apple"],
  };

https://surveyjstest.azurewebsites.net/Examples/Library?id=survey-markdown-matrix&platform=Knockoutjs&theme=defaultV2

Are you requesting a feature, reporting a bug or asking a question?

Bug

What is the current behavior?

OnValueChanging is triggered an additional time after OnValueChanged on custom question types

• onValueChanging is triggered

• onValueChanged is triggered

• onValueChanging is triggered again

What is the expected behavior?

OnValueChanging is only triggered once before OnValueChanged

How would you reproduce the current behavior (if this is a bug)?

Please refer to the this repository with a simple reproduction of the bug. I added one use case of known type text and one for a custom type with it's questionJSON being of type text for comparison.

I am currently overriding this behaviour with the following piece of code:

valueChangingHandler = (sender, options) => {
    if(options.oldValue === options.value) {
        console.warn('onValueChanging execution with equal values', options.question, options.oldValue, options.value)
        return;
    }
    ...
} 

Provide the test code and the tested page URL (if applicable)

Specify your

I am using survey-core as a backbone for a custom survey system.

• browser: /
• browser version: /
• surveyjs platform (angular or react or jquery or knockout or vue): /
• surveyjs version: 1.9.27 (most recent)

Are you requesting a feature, reporting a bug or asking a question?

Reporting a bug.

What is the current behavior?

onShowingPreview doesn't get called when onServerValidateQuestions is set.

What is the expected behavior?

onShowingPreview should be called even if onServerValidateQuestions is set.

How would you reproduce the current behavior (if this is a bug)?

Using the test page provided below, you'll notice that onShowingPreview is never printed unless you remove the assignment of the onServerValidateQuestions event on the survey.

Provide the test code and the tested page URL (if applicable)

Tested page URL: https://plnkr.co/edit/6Sy4Rx5lK9rjA9eD

Test code

Survey
    .StylesManager
    .applyTheme("modern");

//assign call to onServerValidateQuestions callback
function surveyValidateQuestion(survey, options) {
    options.complete();
}

//assign call to onShowingPreview callback
function showingPreview(survey, options){
    console.log("onShowingPreview");
}

var json = {
 "pages": [
  {
   "name": "page1",
   "elements": [
    {
     "type": "boolean",
     "name": "question1",
     "isRequired": true
    }
   ]
  },
  {
   "name": "page2",
   "elements": [
    {
     "type": "boolean",
     "name": "question2",
     "isRequired": true
    }
   ]
  }
 ],
 "showPreviewBeforeComplete": "showAllQuestions"
};

window.survey = new Survey.Model(json);

survey
    .onComplete
    .add(function (sender) {
        document
            .querySelector('#surveyResult')
            .textContent = "Result JSON:\n" + JSON.stringify(sender.data, null, 3);
    });

survey
    .onShowingPreview
    .add(showingPreview);

survey
    .onServerValidateQuestions
    .add(surveyValidateQuestion);

$("#surveyElement").Survey({model: survey});

Specify your

• browser: Microsoft Edge
• browser version: 100.0.1185.50
• surveyjs platform (angular or react or jquery or knockout or vue): jquery
• surveyjs version: 1.9.20

In defaultV2 remove rows actions rendered as icons. A new setting is introduced to render these actions as buttons. Survey.settings.matrixRenderRemoveAsIcon = false;.

The original issue was reported on SurveyJS Support forum.

{
    elements: [
      {
        type: "matrixdynamic",
        name: "question1",
        rowCount: 1,
        columns: [
          {
            name: "Column1",
          },
          {
            name: "Column2",
            readOnly: true
          },
        ],
        cellType: "text",
      },
    ],
  }

The second column becomes editable after the following code:

survey.mode = "display";
survey.mode = "edit"

shortcut text should contain question type instead of generated new question name

based on the https://surveyjs.answerdesk.io/ticket/details/T9276

Right now, Creator V2 has "text" as default question type in "Add Question" button and there is no way to change it. We need to add a new setting to allow chaning this type. SurveyCreator.settings.designer.defaultAddQuestionType = "dropdown";

Use the following code to hide "Add New Question" buttons on page and panel on design surface: SurveyCreator.settings.designer.showAddQuestionButton = false;

onProcessHtml event not fired for html question in knockout

Are you requesting a feature, reporting a bug or asking a question?

Bug

What is the current behavior?

When creating a matrix multiple choice question you can override the choices for a column by settings the cell type to dropdown instead of default. Then using the translation tab you can translate these choices.

What is the expected behavior?

I expected the translations for the column specific choices to be used, but they are not. Note that even the primary choices are not translated (tested via the preview tab)

How would you reproduce the current behavior (if this is a bug)?

{
 "logoPosition": "right",
 "pages": [
  {
   "name": "page1",
   "elements": [
    {
     "type": "matrixdropdown",
     "name": "question1",
     "columns": [
      {
       "name": "Column 1",
       "cellType": "dropdown",
       "choices": [
        {
         "value": "item1",
         "text": {
          "default": "A",
          "nl": "A1"
         }
        },
        {
         "value": "item2",
         "text": {
          "default": "B",
          "nl": "B2"
         }
        },
        {
         "value": "item3",
         "text": {
          "default": "C",
          "nl": "C2"
         }
        }
       ]
      },
      {
       "name": "Column 2"
      },
      {
       "name": "Column 3"
      }
     ],
     "choices": [
      {
       "value": 1,
       "text": {
        "default": "E1",
        "nl": "D1"
       }
      },
      {
       "value": 2,
       "text": {
        "default": "E2",
        "nl": "D2"
       }
      },
      {
       "value": 3,
       "text": {
        "default": "E3",
        "nl": "D3"
       }
      },
      {
       "value": 4,
       "text": {
        "default": "E4",
        "nl": "D4"
       }
      },
      {
       "value": 5,
       "text": {
        "default": "E5",
        "nl": "D5"
       }
      }
     ],
     "rows": [
      "Row 1",
      "Row 2"
     ]
    }
   ]
  }
 ]
}

Provide the test code and the tested page URL (if applicable)

Tested page URL: https://surveyjs.io/create-survey

Specify your

• browser: Brave
• browser version: latest
• surveyjs platform (angular or react or jquery or knockout or vue): knockout
• surveyjs version: latest

Due a bug, custom widgets are not updated on changing locale if it is located in matrix cell or in dynamic panel.

The following json doesn't work correctly. Binding for nested matrix doesn't work:

{
    elements: [
      {
        type: "paneldynamic",
        name: "panel1",
        panelCount: 2,
        templateElements: [
          { type: "text", name: "q1" },
          {
            type: "matrixdynamic",
            name: "q2",
            bindings: {
              "rowCount": "q1"
            },
            columns: [
              { name: "col1" }
            ]
          }
        ],
      }
    ],
  }

See the screencast: https://www.screencast.com/t/Hre5H7X3fSjF

The following code should add a new property into detail form for itemvalue without addition coding.

Survey.Serializer.addProperty("itemvalue", 
    { name: "prop1", category: "general", choices: ["item1", "item2"], showMode: "form" }
);

New "locale" property is added into Creator. To change locale, please use the following code:

creator.locale = "de";

End-user can't drag on text "The survey is empty. Drag an element from the toolbox or click the button below."

Consider, in your survey/form system you want to hide/show matrix header based on expression and allow your Creator user to set this expression. Right now it will require a lot of code, how, it can be as simple as the following:

Survey.Serializer.addProperty("matrix", { name: "showHeaderIf:condition", category: "logic",
   onExecuteExpression: (obj, res) => { obj.showHeader = res === true; }
});

we need a way to see full tick (y) label with matrix question. And the way we could do it is custom hovertext

SurveyJS uses old approach for completedHtml, completedBeforeHtml and loadingHtml survey properties. As result, Creator property grid doesn't show the default value for these properties.

Creator V2 requires questionTemplate be ready right after cellType property is changed. It means we have to change questionTemplate before chaning cellType.

The bug is reproduced in Creator V2. On selecting column and setting cellType to "text", properties "min" and "max" are not become visible if inputType is "number"

The survey "activePage" is not updated after calling "fromJSON" function as well as navigation bar.

For detailed information see this ticket in the support center

Developers want to add buttons into our navigation bar, for example, "Save" button and the only current solution is to hide our navigation bar and let them to render their own. There should be an easy way to do it. The current solution is to use our action container. It will reduce code in platforms.

Are you requesting a feature, reporting a bug or asking a question?

Bug

What is the current behavior?

The onAfterRenderSurvey event should contain an options object described by this:

The event is fired right after survey is rendered in DOM. sender - the survey object that fires the event. options.htmlElement - a root HTML element bound to the survey object.

Instead I get an array of 3 elements, the root element is in the middle, surrounded by 2 text nodes.

What is the expected behavior?

This is what vue does:

https://plnkr.co/edit/0u9vnEWqshAzzcKX

This is what knockout does: https://plnkr.co/edit/x11Iojb6UqbG28lO

How would you reproduce the current behavior (if this is a bug)?

See plunkers above

Specify your

• surveyjs platform (angular or react or jquery or knockout or vue): knockout
• surveyjs version: v1.9.22

A checkbox type question, I can't clear it's comment value by clearValue/setComment

Are you requesting a feature, reporting a bug or asking a question?

question

What is the current behavior?

click clear comment button should clear its comment value, but not

What is the expected behavior?

click clear comment button can clear its comment value

How would you reproduce the current behavior (if this is a bug)?

1. input some value in the other/comment box
2. click clear comment
3. the comment value should be removed

Provide the test code and the tested page URL (if applicable)

Tested page URL: https://codesandbox.io/s/xenodochial-chebyshev-4kbwle

Test code

            this.survey.setComment("car", null);
            this.survey.clearValue("car");

Specify your

• browser: chrome
• browser version: 99.0.4844.84 (Official Build) (64-bit) (cohort: Stable)
• surveyjs platform (angular or react or jquery or knockout or vue): react
• surveyjs version: 1.9.22

https://www.figma.com/file/7QOeoDDCaPuqzWAROR0kDY/SJS-Creator?node-id=13519%3A109427

"When you replace a question type to 'Image Picker' using the dropdown (not the toolbar on the left but the dropdown on a question), it doesn't show you the default images and just shows you an option to add a new image" https://surveyjs.answerdesk.io/internal/ticket/details/T9149

Because we renamed the Test Survey tab, users no longer test surveys - they preview them.

We need to align the message to the center. Compare it to the empty Translation tab:

Let's change the text too: "The survey doesn't contain visible pages or questions"

On setting expression for panel dynamic in logic tab on empty actions section, a JavaScript error is raised.

Settings binding when property grid is modal raised an exception.

"None" is visible/invisible based on "hasOther" property and not "hasNone"

Step to reproduce:

1. go to Nps Example in Creator
2. select the second question, checkbox
3. Go to choices and clear them all, Click on "Clear" button
4. Add new choice

Result the choices action bar will convert to "..."

If value is object in itemvalue, for example: cost newValue = new Survey.ItemValue({ id: 1, value: 5, text: "MyValue"}); then it doesn't work correctly if Survey.settings.itemValueAlwaysSerializeText = true;

There is no context except expression on creating "ExpressionExecutor". Right we set expression as a property after the object was created. It is too late. We have to make expression read-only and pass it into constructor, it gives the ability to use different expression engines based on expression.

The bug can be reproduced in Creator V2 on designer. Drop checkbox question, set column to 2 and clear choices. You will see that "Select All", "None", "Others" items will be rendered twice.

The following JSON doesnt' work correctly. maxRendered value equals to today, instead of today + 30 days.

{
    name: 'question1',
    type: 'text',
    inputType: 'date',
    title: 'Select a date:',
    isRequired: true,
    minValueExpression: 'today()',
    maxValueExpression: 'today(30)',
},

Screencast Test project

Steps to reproduce:

1. Open the Survey Creator: https://surveyjs.io/create-survey
2. Click Add Question for Page 2. Page shouldn't contain any questions before you do that.

Creator V1 has creator.onDragDropAllow event. It is missed in V2.

https://codesandbox.io/s/hidden-wind-qhh3vb

Steps to reproduce:

1. Open the console
2. Click the Add New Survey button
3. Click Add Question in Survey Creator

The following event has been added into Creator:

  /**
   * The event is called when creator is going to change the active tab.
   * <br/> sender the survey creator object that fires the event
   * <br/> options.tabName the name of new active tab
   */
  public onActiveTabChanging: : Survey.Event<(sender: CreatorBase, options: any) => any,  any>;

There is error when you try to add more question type based on rating TypeError this.creator.getLocString is not a function

Code that adds new instance: Survey.ComponentCollection.Instance.add({ name: "newrating", title: "SuperRating", elementsJSON: [ { "type": "rating", "name": "superrating", "title": "1", "isRequired": true, "rateMin": 0, "rateMax": 10, "minRateDescription": "1", "maxRateDescription": "2" } ] });

Provide the test code and the tested page URL (if applicable)

Tested page URL: https://codesandbox.io/s/shy-surf-lgp5vn?file=/src/SurveyCreatorComponent.jsx

Versions that also reproduce issue

"survey-core": "^1.9.8",
"survey-creator-react": "^1.9.8-beta.1",
"survey-react": "^1.9.8",
"survey-react-ui": "^1.9.8",

autoComplete property editor should show the list of possible values.

We do not need a root Creator property _stateValue to be reactive. It triggers re-rendering Creator on a property change of any object.

Filter is not applied to matrixdropdown visualizer content (if other question is filtered)

See the https://surveyjs.answerdesk.io/internal/ticket/details/T8823 thread for more details

based on the https://surveyjs.answerdesk.io/ticket/details/T9017

also see https://dkane.net/2020/better-horizontal-bar-charts-with-plotly/

See the https://surveyjs.answerdesk.io/ticket/details/t8264/saving-panel-state thread for more details

Vertical bar chart Set Y axis value as predefined [X= 1 to 10, y=0% , 25 %, 50 %, 75% , 100%]

See the https://surveyjs.answerdesk.io/internal/ticket/details/T9142 thread for more details

Visualize selectbase question (radiogroup, dropdown and checkbox) as a table with percent and answer count.

See the https://surveyjs.answerdesk.io/ticket/details/t9084/is-it-possible-to-show-table-format-data-in-analytic-pack thread for more details

Current Behavior - the SurveyJS example demonstrates this issue perfectly:

It should be obvious that the ordering is horrendous - No user starts typing in "Peugeot" with a "t" - they would start typing Toyota with a "t". Ultimately, this issue makes this library unusable with large autocomplete sets, as users need to type in a significant portion of the entire item before autocorrect even displays the item they want in the list.

EasyAutocomplete can be reconfigured to sort properly - is there any interest in doing this, or adding support for a better autocomplete option, given how EasyAutocomplete has not been updated (other than by dependabot) since October 5th, 2019 (so for nearly 3 years), and also fails to provide the basic feature of enter selects first element?

The following JSON doesn't work:

        {
            "name": "date",
            "type": "datepicker",
            "inputType": "date",
            "title": "Your favorite date:",
            "dateFormat": "mm/dd/yy",
            "isRequired": true,
            "minValueExpression": "today()",
            "maxValueExpression": "today(10)"
        }        

If "multiselect" property is set to true then function "supportGoNextPageAutomatic()" should return false.

By default in Creator V2 we show on designer surface for select base questions (radigroup, checkbox, dropdown) Select All, None and has Others. By setting: Survey.settings.showDefaultItemsInCreatorV2 = false; they will not be shown.

Setting matrix.cells doesn't update cells text in matrix. The question is not re-rendered.

On changing locale navigation title and description are updated for the current page only, but they have to be updated for all pages.

On setting/removing cells property do not convert matrix to matrix rubric and vice versa

Are you requesting a feature, reporting a bug or ask a question?

Bug

What is the current behavior?

The cursor changes to pointer, which indicates that you can interact with it. Additionaly clicking on it gives feedback, like something should happen (but of course doesn't).

What is the expected behavior?

No click events and no changing cursor.

How would you reproduce the current behavior (if this is a bug)?

Add a question of type file.

Provide the test code and the tested page URL (if applicable)

Tested page URL: https://surveyjs.io/create-survey-v2

Specify your

• browser: Chrome 98
• editor version: 1.9.14

https://user-images.githubusercontent.com/10886924/154705358-96b55247-7313-420d-99a8-eebbd2367066.mp4

https://www.figma.com/file/7QOeoDDCaPuqzWAROR0kDY/SurveyJS?node-id=9414%3A51795

• fix shadow
• fix corner rounding
• check styles in safari

https://www.figma.com/file/7QOeoDDCaPuqzWAROR0kDY/SurveyJS?node-id=2281%3A116403 Referenced to https://github.com/surveyjs/survey-library/issues/3965

Are you requesting a feature, reporting a bug or ask a question?

Bug in V2 React. Seems to work fine in V2 Knockout.

What is the current behavior?

1. On a new empty survey designer page add a question. (surveyjs example: here)
2. Switch to any other tab and return back to the designer page.
3. Delete question1 and then page1.
4. Survey still shows page2. When I switch the tab now and return back it shows empty. But when I again add a question the empty page message still appears and the layout seems to be broken.

Please refer attached video:

https://user-images.githubusercontent.com/13827554/157854882-f8ecc370-8c7c-4598-8257-603e80ca44cf.mp4

What is the expected behavior?

The survey designer should be empty on deleting all pages and questions immediately.

How would you reproduce the current behavior (if this is a bug)?

Mentioned above with video

Provide the test code and the tested page URL (if applicable)

Tested page URL: https://surveyjs.io/Examples/CreatorSinglePage?id=options&platform=ReactjsV2&theme=modern

Test code

your_code_here

Specify your

• browser: Chrome 99
• editor version: 1.9.19

Logic tab doesn't support Page enableIf property in V1 and V2.

Allow to define different brackets from "".

SurveyCreator.settings.logic.openBracket = "[";
SurveyCreator.settings.logic.closeBracket = "]";

defaultValueExpression property is not showing in property grid for matrix column

https://www.figma.com/file/7QOeoDDCaPuqzWAROR0kDY/SurveyJS?node-id=2641%3A1703

The order of triggers execution is important. They perform one by one. That is why we have to allow Creator users to change the order.

• check pager styles
• leave space between pager and survey

Add margin in 4px between toolbox items

https://www.figma.com/file/7QOeoDDCaPuqzWAROR0kDY/SurveyJS?node-id=2341%3A99230

The bug was reported on SurveyJS Support forum

• allow only one expаnded row
• collapse all rows after D&D start

https://surveyjs.io/Examples/Library?id=questiontype-matrixdynamic-detail&platform=Reactjs&theme=defaultV2

based on the https://surveyjs.answerdesk.io/internal/ticket/details/T8975

  Survey.Serializer.addProperty('question', {
    name: 'someProp',
    displayName: ' ',
    type: 'itemvalues',
  });
  var editor = new SurveyCreatorCore.PropertyGridEditorMatrixItemValues();
  editor.getAllowRowDragDrop = function (prop) {
    return prop.name !== "someProp";
  }
  SurveyCreatorCore.PropertyGridEditorCollection.register(editor);

There is a code that using window object without checking that it exists.

If you set the showSidebar to false , the sidebar will still expand.

The following code will generate error in console. We do not support content question component correctly.

    ComponentCollection.Instance.add({ name: 'comp', questionJSON: { type: 'rating', choices: ['A', 'B'] } });
    const json: any = {
        questions: [
            {
                titleLocation: 'hidden',
                name: 'comp',
                type: 'comp'
            }
        ]
    };
    const survey: SurveyPDF = new SurveyPDF(json, {});

https://www.figma.com/file/7QOeoDDCaPuqzWAROR0kDY/SurveyJS?node-id=10034%3A78270

https://www.figma.com/file/7QOeoDDCaPuqzWAROR0kDY/SurveyJS?node-id=10034%3A78153

visibleIf in the following JSON doesn't work on changing comment:

{
    "elements": [
      {
        "type": "radiogroup",
        "name": "question1",
        "choices": [
          "item1",
          "item2",
          "item3"
        ],
        hasComment: true
      },
      {
        type: "text",
        name: "question2",
        visibleIf: "{question1-Comment.length} > 3"
      }
    ]
  }

Are you requesting a feature, reporting a bug or asking a question?

bug

What is the current behavior?

Package survey-knockout-ui v1.9.18 doesn't build with TypeScript, with the following error:

node_modules/survey-knockout-ui/survey-knockout-ui.d.ts(16,25): error TS2300: Duplicate identifier 'Model'.
node_modules/survey-knockout-ui/survey-knockout-ui.d.ts(18,10): error TS2300: Duplicate identifier 'Model'.

What is the expected behavior?

Package survey-knockout-ui builds properly with TypeScript (like it did with v1.9.14)

Specify your

• browser: Chrome
• browser version: 98
• surveyjs platform (angular or react or jquery or knockout or vue): knockout
• surveyjs version: 1.9.18

Allow to override our default expression executor

Complete button is visible after this line code:

survey.mode = "display";

It should become invisible.

calcInArray function doesn't work for non-numeric values as result "count" tota type in column works incorrectly. Here is the related issue on SurveyJS support forum.

similar to rendered rows

• padding between actions & conditions https://www.figma.com/file/7QOeoDDCaPuqzWAROR0kDY/SurveyJS?node-id=7994%3A51953
• "Add new rule" button disabled if new rule doesn't saved
• hover & focus states of expand buttons conflict with each other

based on the https://surveyjs.answerdesk.io/ticket/details/T8839

Steps to reproduce:

1. Open creator
2. Click Clear Survey button (at this step everything works good)
3. Add some questions
4. Click Clear Survey button again
5. There will be page 2

For detailed information see this thread in the support center

based on https://surveyjs.answerdesk.io/ticket/details/T8889

I just found out that even 2-way-data-binding is not working as expected: if you have the tagbox set with multiple values allowed, even if you deselect every single option, survey.data still contains the latest selected value.

Are you requesting a feature, reporting a bug or ask a question?

v2 bug

What is the current behavior?

In pageEditMode single, when opening a blank editor, navigating to the "Preview" tab throws a runtime error and is not possible.

ERROR TypeError: Cannot read properties of undefined (reading '0') at SurveyCreator../src/creator-base.ts.CreatorBase.singlePageJSON (survey-creator-core.js:11374:1)

This seems to be the problematic line in the code: https://github.com/surveyjs/survey-creator/blob/master/packages/survey-creator-core/src/creator-base.ts#L1769

What is the expected behavior?

In pageEditMode single, when opening a blank editor, navigating to any tab should work without errors being thrown.

How would you reproduce the current behavior (if this is a bug)?

• Set pageEditMode to single
• Initialize the editor with a blank JSON (I tested null and {})
• Without adding any questions, navigate to the "Preview" tab

Specify your

• browser: Chrome 98
• editor version: 1.9.15-beta.0

Are you requesting a feature, reporting a bug or ask a question?

v2 bug

What is the current behavior?

I have set pageEditMode to single. Since version 1.9.15-beta.0, in most of the cases the user is not able anymore to see or fill out page information, which is nice. But there is one edge case: After removing the last question, the right menu switches to "page" mode, and the user can fill out page information.

What is the expected behavior?

In pageEditMode single, after removing the last question, the right menu switches to "survey" mode.

How would you reproduce the current behavior (if this is a bug)?

• set pageEditMode to single
• Open a blank survey
• Add a question
• Remove the question

The right menu now is in "page" mode.

Specify your

• browser: Chrome 98
• editor version: 1.9.15-beta.0

Are you requesting a feature, reporting a bug or asking a question?

Bug. It looks like types have been changed, and no longer correspond to the documentation.

What is the current behavior?

Fails to build with TS after updating from 1.9.12 to 1.9.14

TS2339: Property 'Model' does not exist on type 'typeof import("/home/anton/.../node_modules/survey-react/survey.react")'.

What is the expected behavior?

To build without error

How would you reproduce the current behavior (if this is a bug)?

Try and use with TS

Provide the test code and the tested page URL (if applicable)

Test code

const model = new Survey.Model(modelObjects);

Specify your

• surveyjs platform (angular or react or jquery or knockout or vue): react
• surveyjs version: survey-react 1.9.14

We required to create all cell questions to calculate progress info. If there are a lot of matrices it kills the performance on loading surveys. However, we can generate cell questions on showing matrices only and calculate progress info based on row count, matrix value and other column information without creating cell question and rendered tables.

Re-export into "survey-react-ui", "survey-knockout-ui", "survey-vue-ui"

export { SurveyModel, Model, SurveyWindowModel } from "survey-core";
export { settings } from "survey-core";
export { surveyLocalization, surveyStrings } from "survey-core";

jquery, knockout и angular - not visible https://surveyjs.io/Examples/Library?id=survey-quiz&platform=jQuery&theme=modern

React, Vue - visible, but not updating https://surveyjs.io/Examples/Library?id=survey-quiz&platform=Reactjs&theme=modern

1.9.6: https://plnkr.co/edit/1gR7x2ftKoB2OBIc 1.9.14: https://plnkr.co/edit/TTQ6eaaQNPRi2LBf

Quiz example: https://plnkr.co/edit/1gR7x2ftKoB2OBIc?preview

The goal is to specify different complete pages based on the number of correct answers. The example uses the completedHtmlOnCondition property for this, but the complete page always display "Congratulations! You answered all the questions correctly!". Expressions in completedHtmlOnCondition use quiz-specific fields ({correctedAnswers} and {questionCount}), as described in the Create a Quiz tutorial. But if we try to check if the fields are available:

survey.runExpression("{correctedAnswers}")

... we will get null.

Are you requesting a feature, reporting a bug or ask a question?

It is something between a (missing) feature and a bug.

What is the current behavior?

Currently it is possible to configure surveyJS to be in single mode. This is handy, because in our case we don't need page functionality at all. Even though we disable it, we are still stuck with the following options from multi page mode

• page title and description can be configured (additionally to the survey title and description, which is the same in our case)
• page1 can be selected in the top right menu when opening the properties editor
• pages are part of the json instead of the elements property directly in the survey json

Here is a screenshot displaying these points

What is the expected behavior?

Page functionality is completly removed if pageEditMode is set to 'single'. This means

• page title & description are unavailable
• page1 can't be selected in the menu
• pages are not part of the json and instead the elements property containing the questions is on the root of the json

Provide the test code and the tested page URL (if applicable)

Tested page URL: https://surveyjs.io/Examples/Survey-Creator?id=singlepage&platform=KnockoutjsV2&theme=modern

Test code

pageEditMode: 'single',

Specify your

• editor version: 1.9.8-beta.1

We removed inherited classes of SurveyModel in platforms and now it is possible to use the same SurveyModel in all platforms. As result we can simplify our code in Creator V2, remove generic CreatorBase and create survey model in core and not in react/knockout packages. It will remove some code duplication.

Change knockout template and replace visible data-bind in div vs <-- ko if -->

See the examples of unexpected behavior in this ticket

https://www.figma.com/file/7QOeoDDCaPuqzWAROR0kDY/SurveyJS?node-id=10034%3A78347 https://www.figma.com/file/7QOeoDDCaPuqzWAROR0kDY/SurveyJS?node-id=10034%3A78349

matrices columns are not re-rendered on getting column choices via choiceByUrl if showInMultipleColumns property is set to `true'. The bug was reported in SurveyJS support forum.

If there are many panel dynamics binded to the same question value then update visible indices can be called hundred times, if there are visibleIf expressions in dynamic panel template elements. Please read more on SurveyJS Support forum.

Are you requesting a feature, reporting a bug or ask a question?

I have found a bug while using Creator V2 where the Serializer property is not on the Survey component. I am trying to add code from the minimalistic example into the V2 creator found here(https://surveyjs.io/Examples/Survey-Creator?id=singlepage&platform=ReactjsV2&theme=modern#content-js).

I also noticed in the CreatorV2 examples if you select ReactV2 and edit in Codesandbox the page above is failing.

What is the current behavior?

TypeError: Cannot read properties of undefined (reading 'findProperty')
>  99 | Survey.Serializer.findProperty("itemvalue", "visibleIf").visible = false;
  100 | Survey.Serializer.findProperty("itemvalue", "enableIf").visible = false;
  101 | Survey.Serializer.findProperty("itemvalue", "text").visible = false;

What is the expected behavior?

Hide item value properties

How would you reproduce the current behavior (if this is a bug)?

Try to access Serializer from the survey-react-ui library

Provide the test code and the tested page URL (if applicable)

import React from "react";
import * as SurveyCreator from "survey-creator-react";
import * as Survey from "survey-react-ui";

const options = {
  showJSONEditorTab: false,
  showLogicTab: false,
};

const creator = new SurveyCreator.SurveyCreator(options);

// Hide some properties of the itemvalue object
// Design itemvalue[] property editor
// Hide visbileIf, enableIf and text properties
Survey.Serializer.findProperty("itemvalue", "visibleIf").visible = false;
Survey.Serializer.findProperty("itemvalue", "enableIf").visible = false;
Survey.Serializer.findProperty("itemvalue", "text").visible = false;

export default function SurveyJS() {
  return (
    <React.Fragment>
      <React.StrictMode>
        <SurveyCreator.SurveyCreatorComponent creator={creator} />
      </React.StrictMode>
    </React.Fragment>
  );
}

Specify your

• browser: Chrome
• editor version:

• "survey-core": "^1.9.3",
  

  "survey-creator-react": "^1.9.3-beta.1", "survey-react": "^1.9.4", "survey-react-ui": "^1.9.3",

https://surveyjs.io//Examples/CreatorSinglePage?id=localization&platform=KnockoutjsV2&theme=modern

Are you requesting a feature, reporting a bug or ask a question?

bug

What is the current behavior?

When theming the creator, the colors are not applied to the choices popup. It seems that there the variables aren't used. In the screenshot you can see, that the cancel and apply buttons don't have the lightgreen color, but stay in their default color.

What is the expected behavior?

Custom colors are applied to the cancel and apply buttons aswell

How would you reproduce the current behavior (if this is a bug)?

1. Go to the test page url
2. Add question with choice (radio group, checkbox, etc)
3. Open the choices bulk edit modal with this button

Provide the test code and the tested page URL (if applicable)

Tested page URL: https://www.surveyjs.io/Examples/Creator?id=editor-custom-theme-css-vars&platform=KnockoutjsV2&theme=modern#content-result

Specify your

• browser: Chrome 98
• editor version: 1.9.10-beta.1

Are you requesting a feature, reporting a bug or ask a question?

Bug vor v2

What is the current behavior?

In the translation tab, after setting readOnly to true, the translation values can still be edited by the user.

What is the expected behavior?

In the translation tab, after setting readOnly to true, nothing can be edited

How would you reproduce the current behavior (if this is a bug)?

1. enable translation tab
2. enable readOnly

https://codesandbox.io/s/cool-tesla-d5y4k?file=/src/SurveyCreatorComponent.jsx

Specify your

• editor version: 1.9.12-beta.1

re-submit of #2653 which was closed unfixed

Are you requesting a feature, reporting a bug or ask a question?

regression in v2

What is the current behavior?

I am using TypeScript. To set the locale of the editor, I use the following code:

import { editorLocalization } from 'survey-creator-knockout';

editorLocalization.currentLocale = 'de';

It worked fine before v1.9.12-beta.1, but now editorLocalization is undefined, and my code produces a runtime error.

I also tried the following: import { editorLocalization } from 'survey-creator-core';, but it throws lots of build errors.

What is the expected behavior?

I can set the editor locale with TypeScript

How would you reproduce the current behavior (if this is a bug)?

See code above

Specify your

• editor version: 1.9.12-beta.1

Are you requesting a feature, reporting a bug or ask a question?

Feature improvement

What is the current behavior?

When inline editing in creator V2, it is hard to jump to a special place in string with the mouse. This is handy for fixing a typo or changing the field in general. Only when using the keyboard I succeeded. I made a little screen record of that.

https://user-images.githubusercontent.com/10886924/153589626-a6bada9c-c692-417f-bbae-5dd0cbda7a41.mp4

What is the expected behavior?

Click on a field should enable inline edit and select the content. A second click should jump at the position in the string, where you click.

Provide the test code and the tested page URL (if applicable)

Tested page URL: https://surveyjs.io/create-survey-v2

Specify your

• browser: Chrome 98
• editor version: 1.9.12

For detailed information see the ticket

https://www.figma.com/file/7QOeoDDCaPuqzWAROR0kDY/SurveyJS?node-id=10034%3A77791

The following expression rises an exception: 0.1 + 'abc'

For detailed information see the support center

For detailed information see the ticket

For detailed information see the ticket on the support center

Current:

Expected:

https://www.figma.com/file/7QOeoDDCaPuqzWAROR0kDY/SurveyJS?node-id=10957%3A97388

• #2335
• #2336
• #2337
• #2338
• #2339
• #2347
• #2348
• #2346
• #2345
• #2344
• #2343
• #2342
• #2341
• #2340
• #2379

https://www.figma.com/file/7QOeoDDCaPuqzWAROR0kDY/SurveyJS?node-id=7994%3A51952

https://surveyjs.answerdesk.io/ticket/details/t8684/dynamic-panel-panel-count-binding-resets-becomes-corrupt-after-focusing-other-elements

Property grid tries to focus the first property editor in the category. If this property editor is a non-focused questions like hml or expression questions, then a JavaSscript error "access property for undefined object" is raised.

Are you requesting a feature, reporting a bug or ask a question?

Bug report for v2

What is the current behavior?

When setting readOnly to true, I'm still able to work with the Translation tab, e.g. add new languages or maintain translations.

What is the expected behavior?

When setting readOnly to true, no changes can be made in the Translation tab.

How would you reproduce the current behavior (if this is a bug)?

1. enable translation tab
2. enable readOnly mode

Specify your

• browser: Chrome 98
• editor version: 1.9.8-beta.1

If question names as the following:' "question1.A", "question2.B", "question11.C", "question3", then "question11.C" becomes the second item instead of the last one. The correct order should be: "question1.A", "question2.B", "question3", "question11.C".

getPropertyValue() function in localization converts "topOn" into "Top on", but it should not change anything on string like "Top On".

"Add new Question" should work exactly like dropping a question from toolbox. It should use the same json. For example after setting this code new text questions should have place holder: creator.toolbox.getItemByName("text").json.placeHolder = "Test holder"; It should not matter how a text question is added by using toolbox or "Add new question" button on a page.

see https://github.com/surveyjs/survey-library/pull/3868#issuecomment-1013150855 and https://github.com/surveyjs/survey-library/pull/3868#issuecomment-1013161174

It seems going from 1.8.56 to 1.9.6, the constructor for VueSurveyModel has changed, and it no longer accepts parameters.

From Version 1.8.56 (from https://github.com/surveyjs/vue-typescript-example)

export declare class VueSurveyModel extends SurveyModel {
    renderCallback: () => void;
    render(): void;
    protected onLoadSurveyFromService(): void;
    protected onLoadingSurveyFromService(): void;
    get css(): any;
    set css(value: any);
    setDataValueCore(valuesHash: any, key: string, value: any): void;
    deleteDataValueCore(valuesHash: any, key: string): void;
    doAfterRenderSurvey(el: any): void;
    doAfterRenderHeader(el: any): void;
}

From version 1.9.6:

export declare class VueSurveyModel extends SurveyModel {
  constructor();
  renderCallback: any;
  render(): void;
  protected onLoadSurveyFromService(): void;
  protected onLoadingSurveyFromService(): void;
  get css(): any;
  set css(val: any);
  setDataValueCore(valuesHash: any, key: string, value: any): void;
  deleteDataValueCore(valuesHash: any, key: string): void;
  doAfterRenderSurvey(el: any): void;
  doAfterRenderHeader(el: any): void;
}

Seems to cause this error in Typescript:

based on https://surveyjs.answerdesk.io/ticket/details/T8656

  var json = {
    "elements": [
      {
        "type": "ranking",
        "name": "smartphone-features",
        "title": "Please rank the following smartphone features in order of importance:",
        "isRequired": true,
        "choices": [
          "Battery life",
          "Screen size",
          "Storage space",
          "Camera quality",
          "Durability",
          "Processor power",
          "Price"
        ]
      },
      {
        "type": "ranking",
        "name": "smartphone-features2",
        "title": "Please rank the following smartphone features in order of importance:",
        "isRequired": true,
        "choices": [
          "Battery life",
          "Screen size",
          "Storage space",
          "Camera quality Camera qualityCamera quality Camera qualityCamera qualityCamera qualityCamera quality Camera qualityCamera quality",
          "Durability",
          "Processor power",
          "Price"
        ]
      }
    ]
  };

survey.clear(true, true) doesn't run conditions, since there is a check "do not run conditions" on completed surveys.

You can easily reproduce it in this example. Just remove all items by pressing Remove the relative button and then You can click on previous navigation button and go to negative records. I think that navigation should be disabled and prevent such behaviour.

See the https://surveyjs.answerdesk.io/ticket/details/t8663/panel-dynamic-navigation-issue thread for more details