Screenshot

Description

chart 3 dot menu is behind the chart title panel in chart maximize mode

Summary

The grayish background oval indicating a selected st.radio label has too much padding on the right hand side by a few pixels. Here's an example:

(Notice how the background rounded rectangle extends further to the right past "Notion" than it does to the left of the sel

In recent versions (can't say from exactly when), there seems to be an off-by-one error in dcc.DatePickerRange. I set max_date_allowed = datetime.today().date(), but in the calendar, yesterday is the maximum date allowed. I see it in my apps, and it is also present in the first example on the DatePickerRange documentation page.

E

Problem

The source link in the docs:

links to the matplotlib source on the website. This is ok, but subsequent navigation of the code is more frustrating than on github. For example I can't figure out how to the get to the folder containing https://matplotlib.org/stable/_modul

The y-axis ticks supports the rotated option, but the doc is missing.

I haven't checked whether other options are missing.

Bugs and Questions

Checklist

• This is not a victory-native specific issue. (Issues that only appear in victory-native should be opened here)

• I have read through the FAQ and Guides before asking a qu

After loading a new file and coming to the Configure Parsing Options page, you have the ability to modify the parsing rules, which I do pretty frequently with the kinds of (mostly tsv-like) files that I get. Most frequently I need to change the "Ignore first" and "Discard initial" parameters and since I usually need both of these and since my files are large and complex enough for the preview upda

When entering a repository path, users should be able to hit TAB for autocomplete, like in bash.

it's becoming more time-consuming and error-prone to manually re-test all the demos following internal refactorings and API adjustments.

now that the API is fleshed out a bit, it's possible to test a large amount of code (non-granularly) without having to simulate all interactions via Puppeteer or similar.

a lot of code can already be regression-tested by simply running all the demos and val