Jump to content

Archived

This topic is now archived and is closed to further replies.

chamois_blanc

fixed-top-pusher at 768px width

Recommended Posts

chamois_blanc

Hello,

 

I found this declaration in the css compile code:

 

   @media (max-width:768px){.pl-fixed-top{position:static} .fixed-top-pusher{display:none} }

 

Shouldn't this be max-width:767px instead? Aren't usually max-width on the odd width size before the next limit (479px, 767px, 1023px, 1299px...), and min-width on the even width size limit itself (480px, 768px, 1024px, 1300px)?

 

Gilles

Share this post


Link to post
Share on other sites
Danny

Hi,

 

No it should be 768px, why do you think it should be something else ? 767px is only used for phones and portrait tablets as far as I remember.

 

See this article for explanation on media queries and device widths - http://css-tricks.com/snippets/css/media-queries-for-standard-devices/


Please search our forums, before posting!

Share this post


Link to post
Share on other sites
chamois_blanc

Hmm this makes no sense to me but I'll do some research.

 

It would be either 767px or 769px. The opposite of max-width:768px is min-width:769px. I don't quite understand the css classifications in the link. Or let me rephrase: I understand it when (min|max)-device-width is used. If the 'device' part is skipped, then it seems to me that (min|max)-width would also apply to a browser window size on a computer, which just depends on whatever the user sets it at. For instance, this definition:

 

/* Smartphones (landscape) ----------- */ @media only screen and (min-width : 321px) { /* Styles */ }

 

could also match a browser window wider than 321px. There is also a hole between 1025px and 1223px in the different definitions. What if the user sets their browser that way?

 

Share this post


Link to post
Share on other sites
Danny

The idea of media queries when using 768px is to target devices not users resizing their browsers. I find it highly unlikely in this day in age, that a user would have a resolution of 768px. Also, PageLines didn't create these media queries widths they're the widths of devices as mentioned on the article I gave you.


Please search our forums, before posting!

Share this post


Link to post
Share on other sites
chamois_blanc

Well then coming back to pagelines defined widths. I found this in the documentation:

 

Responsive

@resLargeDesktop 1200px @resDesktop 979px @resPortraitTablet 767px @resPhoneLandscape 480px

 

Is that wrong then?

Share this post


Link to post
Share on other sites
Danny

There is no wrong or right way to use a pixel width in a media query, you use what you like. All I was pointing out with that article was the standard device widths. You can use whatever width you like in your media queries.

 

If you view the variables.less file, there is a reference to the media queries.

 

// Reference ---------------
// PORTRAIT TABLET TO DEFAULT    -- @media (min-width: 768px) and (max-width: 979px) { }
// LARGE DESKTOP & UP        -- @media (min-width: 1200px) { }
// PHONE TO NETBOOK & PORTRAIT TABLET -- @media (max-width: 767px) { }
// UP TO LANDSCAPE PHONE        -- @media (max-width: 480px) { }

Please search our forums, before posting!

Share this post


Link to post
Share on other sites

  • Similar Content

    • Michael Kummer
      By Michael Kummer+
      Hi guys!
      I have noticed that my primary sidebar becomes intermittently invisible when browsing through various blog articles on michaelkummer.com/blog.
      See:
      https://www.dropbox.com/s/z646sgoa3mfjl1j/Screenshot 2018-07-12 15.57.46.jpg?dl=0 and https://www.dropbox.com/s/vdledzzgginvwgv/Screenshot 2018-07-12 15.57.57.jpg?dl=0
      Upon refresh, the sidebar appears. I have been using the following CSS code to hide the sidebar on mobile without any issues. 
      @media only screen and (max-width: 993px) {
      /* hide sidebars */
           .plsb {
              display: none !important;
          }
      }
      I tried to add the following CSS to force the sidebar to show on screens that are wider than 994 pixels but to no avail. Any clue what could be causing this issue?
    • Michael Kummer
      By Michael Kummer+
      Hi guys!
      I am using the LESS/CSS Pagelines extension and tried to add the following code to make use of FontAwesome:
      a.c2a:before {
          content: "\f07a\00a0";
          font-family: "Font Awesome 5 Pro";
          Font-weight: 900;
          font-style: normal;
          font-weight: normal;
          text-decoration: inherit;
          padding-left: 4px;
      }
       
      The issue is that as soon as I have the CSS via the Custom Styling text box, Pagelines (or the extension) strips out the backslashes (\). As a result, I had to abandon the CSS/LESS extension and instead add all my CSS code to a separate .css file.
      Is there a fix or workaround for this?
      Thanks
      Michael
    • glyph.marketing
      By glyph.marketing+
      Hello, I am having a problem similar to that experienced by Michael Kummer here. We have pages that show this automatic scrolling issue (examples here and here) and it is sufficiently annoying that we have seen customers bounce while trying to convert. Strangely, it only happens at specific resolutions, so it can be difficult to reproduce. In general we can only consistently reproduce it on a 4k resolution with a browser width between 1517 and 1536px. 
      Thanks to Michael Kummer's help we were able to set the overflow-anchor property to none in the entire body, which fixed the issue as far as we can tell, but also obviously disabled scroll anchoring for the whole site. I tried applying it to the specific element that looked like it was being reloaded, which was the PL Meganav extension, but that was unsuccessful. 
      Can anyone help us figure out which element or ID we can apply this property to, so that we can fix the scrolling issue but not disable scroll anchoring for the entire site?
      Thank you - 
      Glyph Language Services
    • chamois_blanc
      By chamois_blanc+
      Hello,
      Shouldn't the image PL5 component be using the srcset/picture css directives to pick the correct size for an image? or it does already and I don't know how to use it? Thank you for any advice or enlightenment.
    • Dan Haddock
      By Dan Haddock
      Plugins Active and installed: 
      Akismet Anti-Spam
      Coming Soon Page & Maintenance Mode by SeedProd
      Contact Form 7
      Cookie Law Info
      DMS Professional Tools  
      Enhanced Media Library  
      Flamingo
      Google Analytics for WordPress by MonsterInsights
      Google XML Sitemap
      Jetpack by WordPress.com
      Legull 
      Loginizer   
      MailChimp for WordPress
      PageLines Updater    
      Schema App Structured Data 
      Sucuri Security - Auditing, Malware Scanner and Hardening
      Uber reCaptcha    
      Yoast SEO
      Wordpress Version: 4.8.1
      Pagelines Version: 2.2.4
       
      Good Evening/Afternoon or Morning, 
      I am running into a problem with CSS styling not applying inside of most browsers (Safari, Firefox) when I am logged in to wordpress, and all browsers that I have tested when I am logged off and the site has been made public (Chrome, Firefox and Safari).
      As a result, I have managed to identify the probable cause. It looks as though these browsers are refusing to render my sites compiled CSS file due to it being a HTTP URL rather than HTTPS.
      I have attempted to change this URL to HTTPS in my browser, however it brings back an ERROR: File not found page - https://www.shortfilmblog.com/wp-content/uploads/pagelines/compiled-css-core-1505847507.css
      What would you suggest in this regard? Would this be resolvable from your end?
      Happy to provide any further details required.
×