Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aspect Ratio of map is very bad for wide displays #4

Open
StefanBrand opened this issue Nov 11, 2019 · 4 comments
Open

Aspect Ratio of map is very bad for wide displays #4

StefanBrand opened this issue Nov 11, 2019 · 4 comments

Comments

@StefanBrand
Copy link
Contributor

A suggestion from a community member: Make a split-screen with the map on the left side and the list on the right side.

My opinion: In mobile view, we could even omit the map and simply put a link to it somewhere. This would make the page faster.

@ff2u
Copy link
Contributor

ff2u commented Nov 27, 2019

Now, after solving the "Smartphones display homepage in full width" "bug" I'm not sure if addressing this issue is still relevant.
On my mobile device the page loads fast. Is it slow when loading on a FP1?

@StefanBrand
Copy link
Contributor Author

I'm not talking about mobile phones, but about desktop screens with a very high resolution (similar to this:)

grafik

@ff2u
Copy link
Contributor

ff2u commented Nov 30, 2019

A maximum width could be configured for the map in the html file. But I don't think it looks nice when map and list are showing up beside each other in two columns:

grafik

or

grafik

...well, the second version looks acceptable though...

@StefanBrand
Copy link
Contributor Author

It doesn't have to be split 50:50. I imagine something like the Fairphone shop finder. It has a column of shops on the left and the map big on the right side (~15:85).

Most important part in my opinion is that the map fills the whole page below the top bar, without padding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants