[dev.icinga.com #6282] Switching from compact layout to poor layout looses detail container

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/6282

Created by elippmann on 2014-05-23 10:55:41 +00:00

Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2015-06-29 15:30:16 +00:00 (in Redmine)

---

Steps to repdroduce:

• Visit icingaweb/dashboard#!/icingaweb/monitoring/show/service?host=host_060&service=random_00 for example
• Reduce page resolution until Icinga Web 2 changes to the poor layout
• Notice that the detail container got lost
• Increase resolution until Icinga Web 2 changes back to the compact layout
• Notice that the detail container is not recovered

---

Parent Task: #5543

Relations:

• duplicates #6282

[icinga-migration]

Updated by tgelf on 2014-05-26 07:23:24 +00:00

This is related to the fact that we still need to finish the "responsiveness" implementation when it goes to handle less or more (max three right now) than two columns.

In your scenario the dashboard should vanish when switching to "poor", we will always keep the rightmost column when dropping some. We will (at least initially) NOT remember "what used to be on our left side", as this will probably add quite some complexity when it goes to handle browser history.

Cheers,
Thomas

[icinga-migration]

Updated by elippmann on 2014-05-26 07:37:58 +00:00

tgelf wrote:

This is related to the fact that we still need to finish the "responsiveness" implementation when it goes to handle less or more (max three right now) than two columns.

In your scenario the dashboard should vanish when switching to "poor", we will always keep the rightmost column when dropping some. We will (at least initially) NOT remember "what used to be on our left side", as this will probably add quite some complexity when it goes to handle browser history.

Cheers,
Thomas

In that case we would have to rewrite the history and change the URL when dropping columns. Maybe it's better to render the columns beneath each other ordered from right to left?

[icinga-migration]

Updated by tgelf on 2014-05-26 12:04:12 +00:00

lippser wrote:

In that case we would have to rewrite the history and change the URL when dropping columns. Maybe it's better to render the columns beneath each other ordered from right to left?

As from our related discussion:

• we will not render them stacked but keep only the rightmost container. While doing so we will nonetheless take care of the "restore-lefthand-column(s)-when-restoring-the-full-layout" feature request.

Best,
Thomas

[icinga-migration]

Updated by elippmann on 2014-06-01 13:10:23 +00:00

• Category set to UI
• Target Version set to 2.0-8

[icinga-migration]

Updated by elippmann on 2014-07-22 13:52:46 +00:00

• Target Version changed from 2.0-8 to Backlog

[icinga-migration]

Updated by elippmann on 2015-03-27 14:58:08 +00:00

• Target Version changed from Backlog to 2.0.0-rc1

[icinga-migration]

Updated by berk on 2015-04-20 07:53:18 +00:00

• Priority changed from Normal to High

[icinga-migration]

Updated by berk on 2015-04-20 07:53:52 +00:00

• Priority changed from High to Urgent

[icinga-migration]

Updated by berk on 2015-04-20 08:16:28 +00:00

• Priority changed from Urgent to Immediate

[icinga-migration]

Updated by berk on 2015-04-20 08:16:43 +00:00

• Priority changed from Immediate to Normal

[icinga-migration]

Updated by elippmann on 2015-05-27 07:04:49 +00:00

• Target Version changed from 2.0.0-rc1 to Backlog

We'll tackle this one once we implement support for more than two columns.

[icinga-migration]

Updated by elippmann on 2015-06-29 15:30:10 +00:00

• Relates deleted 5543

[icinga-migration]

Updated by elippmann on 2015-06-29 15:30:17 +00:00

• Target Version deleted Backlog
• Parent Id set to 5543

[icinga-migration]

Updated by elippmann on 2016-02-18 11:34:42 +00:00

• Duplicated set to 11152