Hi,
Came accross an interesting and difficult one for Reflow:
- On a desktop screen 'without zooming' there's a page with a big table of options (let's say 30 or more)
- Each option has a button in the last column to open a non-modal dialog with a chart.
- This non-modal dialog can be placed / moved / dragged 'over' the page on a position of choice.
- So the idea / result is that you have several charts you can watch at the same time (placed over the page according to your wish)
This can work fine IF you have enough screen space.
Now if you zoom in (till 400%) , or are looking at the page on a mobile, the button to trigger the non-modal dialog should still be available BUT there is just not enough screen space left to place the non-modal dialogs.
There might be place for 1, but with 2 you already have a screen space problem to show the charts, with 3 there's just no use to do it and fills the screen so much it's even not possible to handle all the 'floating' content anymore.
Of course this has been a desktop first approach in the first place instead of mobile first, but that's not the question.
The question is: what does 'functionality' exatly mean / the definition in this case? And did we think about this construction creating the SC?
Keeping the functionality to trigger the non-modal dialogs even on a small screen or at 400% zoom does not any sense (and the UX person in this case would like to hide it, as the charts can be seen chart-by-chart on other pages)
Hi,
Came accross an interesting and difficult one for Reflow:
This can work fine IF you have enough screen space.
Now if you zoom in (till 400%) , or are looking at the page on a mobile, the button to trigger the non-modal dialog should still be available BUT there is just not enough screen space left to place the non-modal dialogs.
There might be place for 1, but with 2 you already have a screen space problem to show the charts, with 3 there's just no use to do it and fills the screen so much it's even not possible to handle all the 'floating' content anymore.
Of course this has been a desktop first approach in the first place instead of mobile first, but that's not the question.
The question is: what does 'functionality' exatly mean / the definition in this case? And did we think about this construction creating the SC?
Keeping the functionality to trigger the non-modal dialogs even on a small screen or at 400% zoom does not any sense (and the UX person in this case would like to hide it, as the charts can be seen chart-by-chart on other pages)