Bug in TextBoxCommandInput and StringValueInput inside a table hosted by a group

Bug in TextBoxCommandInput and StringValueInput inside a table hosted by a group

nnikbin
Collaborator Collaborator
368 Views
0 Replies
Message 1 of 1

Bug in TextBoxCommandInput and StringValueInput inside a table hosted by a group

nnikbin
Collaborator
Collaborator

Usign TextBoxCommandInput and StringValueInput inside a TableCommandInput which is a child of a GroupCommandInput produces some unexpected behaviours.

 

For StringValueInput:

Setting isReadOnly to true for StringValueInput will not work if the StreingValueInput is inside a table which is a child of a group.

 

The following picture shows the problem in a modified version of CustomGraphicsSample add-in (left) versus the original version of the sample add-in (right). The difference is that the modified version uses a group to host the table.

 

11.png

 

For TextBoxCommandInput:

Using TextBoxCommandInput inside a TableCommandInput which is a child of a GroupCommandInput produces some problems when the number of rows is greater than TableCommandInput.maximumVisibleRows. It actually creates empty a textbox with a small vertical scrollbar for the rows > maximumVisibleRows.

 

The following picture shows the problem in a modified version of CustomGraphicsSample add-in (left) versus the original version of the sample add-in (right)

 

12.png

0 Likes
369 Views
0 Replies
Replies (0)