Class to determive element visible only for destkop view

4 replies · opened Sep 30, 2016

JjuanleSep 30, 2016

Hello,

You have done an excellent job with http://themes.semicolonweb.com/html/canvas/alternate-mobile-menu.php this is really useful to have different user experience in mobile and desktop (depending on screen resolution).

However, do you have a generic class to for example determine an element that should be visible for large screens?

Example: in destkop view I want to see all content http://themes.semicolonweb.com/html/canvas/blog-small.php however in mobile view I may not want to display the right side bar (not even below) as I want the user to focus only on the main content. Even in the footer I may want to have some elements only in the destkop view.

In conclusion, do you have a class or a way to display some elements only for desktop and that they will automatically disappear if screen resolution is low? that could be extremely handy to tune the user experience to the screen size (large screen more information, small screen less information and only the most important will be displayed).

Thanks
Juan

JjuanleSep 30, 2016

I think I found part of the answer here

http://themes.semicolonweb.com/html/canvas/responsive.php

Still, I could not find a class to display a content for large device and destkop only.

I would like a class such as

".visible-md,lg" Is that possible?

That content will not be display for xs and small, but it will be displayed for big and large.

Large devices, destkop VISIBLE / small, extra small NOT VISIBLE

Thanks
Juan

JjuanleSep 30, 2016

Maybe I could combine .hidden-xs and .hidden-sm with same result, is that possible?

Thanks
Juan

JjuanleSep 30, 2016

I tried combining hidden-xs and .hidden-sm and it worked fine! excellent, I think you can close this ticket then.

Thanks
Juan

JjuanleOct 1, 2016

Thanks, you can mark as resolved

Have the same question, or something new?

Sign in to the Canvas dashboard to reply or open your own topic. Canvas owners get direct help from the SemiColonWeb team.

Reply on the dashboard