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
On a very wide browser the width is still fixed. It is not obvious that the table is cut off and I was very confused that I never found the operator reference documentation I was looking for.
I would suggest either:
refactoring the table into many separate tables either by provider or by column
reformatting the tables into nested lists
truncating the long token names that push the table wide
choosing a theme that is responsive
I'm new to the project and docs so I don't want to force my formatting decisions, but I'm happy to make a PR if someone can suggest what to do.
The text was updated successfully, but these errors were encountered:
In my humble opinion this issue can be fixed with following css changes :
/* override the maximum width restriction for large screen */
.wy-nav-content {
max-width: none;
}
/* override table width restrictions and allow multiple line td */@media screen and (min-width:720px) {
.wy-table-responsivetabletd {
white-space: normal !important;
}
}
Screen shoot of 1080p screen web browser after applying above changes
Same can be tested inside developer option of browser
On firefox
Press F12 on documentation site page
Go to style editor
Choose css and add above code and test the changes.
I will want to delete this page and replace it with a list of operators in another form. Ideally, it would be like we managed to create something similar to the Terraform Registry.
See: #11423
There are many wide tables in the documentation, for example here:
https://airflow.readthedocs.io/en/latest/operators-and-hooks-ref.html#id19
On a very wide browser the width is still fixed. It is not obvious that the table is cut off and I was very confused that I never found the operator reference documentation I was looking for.
I would suggest either:
I'm new to the project and docs so I don't want to force my formatting decisions, but I'm happy to make a PR if someone can suggest what to do.
The text was updated successfully, but these errors were encountered: