[LOGTOOLS-9] UX Vaadin-induced problems Created: 22/Mar/16  Updated: 07/Jun/18  Resolved: 07/Jun/18

Status: Closed
Project: Magnolia Log Tools
Component/s: None
Affects Version/s: 1.0
Fix Version/s: 1.x

Type: Bug Priority: Minor
Reporter: Maxime Michel Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

Two UX issues have arised during the UX improvements to the Log Tools app done in LOGTOOLS-6:

  • first, the editor in the Levels tab is not showing the name of the log file, unless it is set to be editable, which it shouldn't. As mentioned in com.vaadin.ui.Grid.Column#setEditable, this will change in a future Vaadin release.
  • second issue will also potentially be fixed in a Vaadin update. When the Log Levels editor is open and the user leaves the tab for another, then when he comes back, the editor has disappeared and he can't edit any level but the one he was actually editing. No workaround was found for this one, and it would have been ugly anyway. Therefore, we leave it on the side for now, especially as it should only be a really minor issue.

Generated at Mon Feb 12 06:01:18 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.