perpetual.design

We fixed this – some old css was cached! – in Gantry, I believe (or perhaps a caching plugin). Recompiling the CSS in Gantry fixed my issue. Thanks!

• This reply was modified 8 years, 1 month ago by perpetual.design.

Oh! Does it do this via Javscript? Or CSS media queries, with an override? What properties could I accidentally override it to break it like this? In the inspector, it doesn’t show it being overridden…

I kept the default values. I like them. I just wonder why fixed-width is there, seemingly, be default. It’s the property that’s giving me the most trouble.

Bump?

Responsive vs. non responsive.

This image is what I want. I have to explicitly state that these g-block columns are not fixed-width for class .size-33-3. Why?

If I don’t override this property with ‘none’, then the columns are not responsive and become too ‘tall’ and squashed.

On desktops. Smaller breakpoints need to fill the column on this home page.

Fixed width/max width on smaller screens makes all the columns really tall and skinny.

Sorry I took so long to reply!

hardee family medicine

There’s the link. Currently, the blocks are responsive since I override them in my custom stylesheet.

Please close this! I looked at the page source afterwords and finally realized the problem is me!, as in my faulty code – with an extra bracket.

Goes to show ya (me) that some extra reflection and deep breaths work. can’t believe… ~face palm~ XD

I just want to add a comment, I discovered the elusive problem.

I forgot to post that you were correct, in a way. Firefox handles body styles and overflow different than, say, Chrome or IE.

Using this:

@-moz-document url-prefix() {
	html { overflow: hidden; height: 100%; }
	body { overflow: auto; height: 100%; }
}

At the top of my style sheet I was able to overcome the problem that only showed in Firefox (mobile and desktop) but not Chrome or any other browser.

I don’t believe most Gantry users will need this with the Hydrogen theme, however if you make any padding adjustments and/or add many rows of content to a one-page style web site and Firefox acts wonky on anchor links this is the cure.

An obscure problem for a rare need, but it’s fixed, works great and I really appreciate all your help!

It seems the key to this is in main.js for Gantry. All the Offcanvas code is in there. Is there an API call for main.js like Jquery.Uikit ($.UIkit.offcanvas.hide();)? Where I can close the offcanvas menu after clicking anchors? Others have used this solution and it tends to work by closing the menu and then scrolling without bouncing back up.

Here is the link. Sorry, I had it local development only, but I just uploaded it.

As I mentioned before Anchor links work fine on desktop, but on mobile (or technically anything 48rem wide or under – when the offcanvas menu kicks in) anchor links do not stay.

A click scrolls you there and click off the offcanvas mobile menu immediately scrolls you back to the top.

Nevermind, I found this plugin (Add From Server) does the trick. Thanks again. This still was a great plugin

There is no mobile mode on here. It is a responsive theme that adjusts to the screen size. If you need to separate modes you will need a different theme.

I know it is not fixed. It is caused by at least that one line of code. There may be further lines within the plugin that load insecure elements.

Notice: wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in C:\xampp\htdocs\mooresvilleglass.local\wp-includes\functions.php on line 3547

Notice: wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in C:\xampp\htdocs\mooresvilleglass.local\wp-includes\functions.php on line 3547

I have the same issue. It’s just a PHP Notice, and by no means a content killing error on the frontend of the Dashboard backend. Deactivating this plugin makes the notice go away (this is all with WordPress Debug on, of course). Looking over the plugin code I can’t seem to pinpoint what would cause this…

And by the way, I am using WordPress 4.1.1 and the latest plugin to date of this post.