The Fields module should be able to overflow by expanding, just like the Table #194
Labels
Comments
|
Agreed will implement this week |
|
ok, I didn't end up doing it that week. But its done now. Rather the fields and table panels have been merged, so this just happens now. |
spalger
pushed a commit
to spalger/kibana
that referenced
this issue
Mar 3, 2016
- Closes elastic#169 - Add type field to multi_match - Closes elastic#175 - Adding global autocomplete rules for aliases - Closes elastic#194 - Adding time_zone to date_histogram agg - Closes elastic#199 - Removed multi_field type and added copy_to - Closes elastic#170 - Add _bunch endpoint - Closes elastic#174 - Adding _search/template endpoint
harper-carroll
pushed a commit
to harper-carroll/kibana
that referenced
this issue
Jul 11, 2016
Header was written
w33ble
added a commit
to w33ble/kibana
that referenced
this issue
Sep 13, 2018
* feat: convert registry to a class, add wrapper method also add test for the wrapper method * feat: change element registry, wrap registered elements BREAKING CHANGE: changes the exported name of the registry and also how elements are registered (as objects instead of instances) * chore: update elements to export simple objects the registry wraps the objects internally * feat: wrap type objects on register BREAKING CHANGE: removes the public type registry in favor of the common regitry, renames the export, and expects all type definitions to be plain objects * chore: update named export from type registry also always use the common registry * chore: update types, export plain objects * chore: update names export for type registry in init * fix: remove direct reference to filter type use the registry instead * chore: move function registry to common removes duplicate registry logic * feat: wrap function specs on register BREAKING CHANGE: function definitions should be simple objects * chore: make function specs plain objects * chore: make function specs plain objects * chore: fix function registry references * fix: create public export of function registry this is required for plugins public code to access the functions registry * chore: fix a few more function registry imports * feat: expression type registries wrap objects on register BREAKING: registered specs are expected to be plain objects, with a name property * chore: change how spec instances work, add name to object BREAKING: name is no longer the first argument of the constructor, the spec is expected to be a plain object with a name property * chore: convert expression specs to plain objects * chore: auto-wrap args, convert existing args to plain functions BREAKING: args are simply and array of objects now, with a name property
This was referenced Sep 24, 2020
This was referenced Jan 18, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A common configuration is to have a row consisting of a table, and a fields widget controlling it. We typically put that row on the bottom, and set the table to overflow: expand (rather than scroll) so that the whole page scrolls, rather than just the table.
Given that this configuration is probably pretty common, it would be nice if the Fields widget had the same behavior.
The text was updated successfully, but these errors were encountered: