For example, Show Table Schema displays the schema above the menu which can result in menu itself being pushed off the page. In general, it causes the menu to move up and down rather than staying on top.
Could we move the menu (and download options button) from same level as query to same level as table name (like it is for file)? Then all results (annots, schema etc.) would appear below menu (between it and query zone).
Needs more testing, but I had more time today to work on this then I anticipated!
All unknowns turned out to be manageable, so this is ready for a code review.
Because of a related bug found during the development of this solution, we are bumping to deploy to staging (release 293). If you Edit query results of a View on production, the default columns are no longer recognized (because they have unexpected ColumnModel IDs now). The fix is to always clear the IDs during comparison (so if your column looks like a default VIew ColumnModel but with a different ID, the web UI will still treat it as a default column and you will be unable to edit the results going forward).
Added the new “X” close button next to the Query button in the input widget (which sends that event to the Table Entity, where it is handled in the same way as the action menu event):
Verified fixed 293.0/293.0-15x.