You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of expected behavior and the observed behavior
The Panel docs says cols is the number of columns in the text input field, which is quite confusing. The Bokeh docs makes it clearer, cols specifies the width of the text area (in average character width). However, instantiating different TextAreaInput widgets with different cols doesn't seem to make any differences. Looking at the code, not sure if cols got implemented actually. As we allow setting the width of widget with width param. How about dropping the cols entirely?
Complete, minimal, self-contained example code that reproduces the issue
importpanelaspn# looks like we also allow negative/0 colspn.widgets.TextAreaInput(cols=-1).servable()
pn.widgets.TextAreaInput(cols=0).servable()
pn.widgets.TextAreaInput(cols=1).servable()
pn.widgets.TextAreaInput(cols=100).servable()
pn.widgets.TextAreaInput(cols=200).servable()
The text was updated successfully, but these errors were encountered:
ALL software version info
Panel 1.6.2a1
Description of expected behavior and the observed behavior
The Panel docs says
cols
is the number of columns in the text input field, which is quite confusing. The Bokeh docs makes it clearer,cols
specifies the width of the text area (in average character width). However, instantiating different TextAreaInput widgets with differentcols
doesn't seem to make any differences. Looking at the code, not sure ifcols
got implemented actually. As we allow setting the width of widget withwidth
param. How about dropping thecols
entirely?Complete, minimal, self-contained example code that reproduces the issue
The text was updated successfully, but these errors were encountered: