If β)β is one of the initial characters in a text_input widget label, the label does not display; however, if the same β)β exsits later within the label, it displays correctly.
That is a numbered list item in markdown, which apparently labels donβt support. You will have the same issue with a dot "1. Procedure followed". Use a backslash to avoid parsing it that way:
Thank you both for your feedback! Weβve realized that we did not document the behavior of the label param when it is passed unsupported Markdown elements such as ordered lists in this case.
Iβve submitted a PR to document that behavior:
Unsupported elements such as blockquotes, un/ordered lists, etc, are not rendered on the frontend. To display unsupported Markdown elements as literal characters in labels, they need to be backslash-escaped.
E.g. Users may want to use > as the label for st.button . Passing label=">" results in no label being displayed, as the > is interpreted as Markdownβs blockquote character. The solution is to backslash escape: label="\>" .