Steps to reproduce:

1. Try to tab through the home dashboard

Actual Result:

![Screenshot from 2021-07-06 14-28-57](https://user-imag

Screenshot

Description

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

Summary

st.image doesn't work when you pass a URL pointing to an SVG file

Steps to reproduce

st.image("https://streamlit.io/images/brand/streamlit-mark-color.svg")

Expected behavior:

The image loads.

Actual behavior:

<img width="714" alt="Screen Shot 2021-07-06 at 2 35 54 PM" src="https://user-images.githubusercontent.com/690814/124669579-7ae8b180-de6

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

I would like to import a .zst or .zstd file but currently that file type is not recognized to be imported by OpenRefine.

Proposed solution

Perhaps using Apache Commons Compress (we already have usage in ImportingUtilities.java)
https://commons.apache.org/proper/commons-compress/examples.html#Zstandard

Allow importing the .zstor .zstd file from my local computer, as well as fr

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