That's the site (the pfsense blog as opposed to…?), and if you pick around in the javascript for the theme they've purchased,there's all sorts of scrolling f***ery going on there.  I'm sure it varies from browser to browser, OS to OS.  I'm Chrome, OS-X.  It's site-specific. I've seen similar behavior on a handful of other sites, usually WordPress blogs with one of those themes that has a 200+ item bullet list of features to justify the cost of the theme. Just pointing it out, if the blog guy doesn't grok the code they have in place that's fine, just noting it's totally annoying and gratuitous.  It resides in common/common.min.js. I also have no interest in disabling "smooth scrolling" to correct one site.  I like my smooth scrolling elsewhere, TYVM. :)

Yes, I can see it now. Have now started to look at it. //Dan Lundqvist

@jahonix: Small Form Factor like miniGBICs? You probably don't mean that, do you? Small Form Factor meaning more compatible with smaller screens such as smartphones.  Probably a Bootstrap-capable forum that auto-resizes the window and page elements and eliminates the horizontal scrollbars. It's clear what NOYB meant.

I have fixed the issue now, it is caused when remote fonts are blocked for the site.  Strange but glad is a solution.

Probably nginx at its best again…  ::)

Netgate is in Austin, TX which is in the 512 area code. 972 is Dallas, TX. So it's unlikely that someone from Netgate called you from that number.

@hexadecagram: No but I did find a video … ;D Obviously you took the "SCNR" the way it was intended. Anything missing from the "Notification" tab in your profile? It should be pretty much what you were asking for, right?

This has been reported before, so you are not the first to see it.

We still monitor that address, but we're preparing to move the wiki docs to a different system so we're probably not going to be handing out access for a bit though I don't have an ETA on that. I wrote that doc, though. I'll look over the proposed updates in the other thread, but I am not a fan of some changes (like using a third-party IKEv2 client on OS X when the built-in one works fine if you do it right). I'll respond on that thread later.

Thanks.