By Michael Kummer+
every since Chrome introduce scroll anchoring (see chrome://flags) blog posts on my page start scroll automatically as soon as the user scrolls down a bit. It is super annoying and I don't know exactly what triggers the incompatibility with Chrome's latest feature that is supposed to improve usability.
Since I don't know what causes it (Pagelines, or a Plugin), I would like to disable the feature using a CSS override that Google describes as follow:
"Scroll anchoring aims to be the default mode of behavior when launched, so that users benefit from it even on legacy content. A CSS property overflow-anchor can disable scroll anchoring in part or all of a webpage (opt out), or exclude portions of the DOM from the anchor node selection algorithm. This property supports the following values when applied to an element E:
overflow-anchor: auto (the default value) declares that the DOM subtree rooted at E is eligible to participate in the anchor node selection algorithm for any scrolling box created by E or an ancestor of E. overflow-anchor: none declares that the DOM subtree rooted at E is not eligible to participate in the anchor node selection algorithm for any scrolling box created by E or an ancestor of E." Do you guys happen to know how to use that property with the ROOT element so it applies to the whole page?
We had this site on our cloud 9 server and moved it to a Amazon Web Service server using Cloud Front and now the Editor on chrome is missing just says USE GOOGLE CHROME TO EDIT WITH DMS. Have tried multiple computers and same results. Any solutions why we would be have this problem? Won't work on any page.
I just went live with this site. http://bikenet.org/
I can see the video background in Firefox, Chrome and IE on my computer as well as my husband's computer and my phone. So I am not able to see any problem.
But, my client says she cannot see the video background in Chrome?? Any ideas?
Let me know. Thanks!
Was on the phone with client yesterday reviewing the site and the server slowed way down. Did a couple updates that may not have taken. Now cannot get back into the DMS editor for http://cassclayton.com/dev/ I can see the site in chrome and firefox but the background image is no longer there. Can get into dashboard in chrome and firefox. Cannot get into DMS editor in chrome - get "Oops, There may be an issue loading." error no matter how many times I try. My internet connection is not the fastest, but I can access other sites I've built in DMS - just not http://cassclayton.com/dev/
My question is,
1) is there a safe way to reinstall DMS that will not trash the work done on the site?
2) Is there a way to see if something in the database got corrupted and how to fix? Since I can't get into DMS editor, can't get to the Flush Cache page to try that.
Just turned on
I haven't seen this come up on the forums, but since Chrome's required for PageLines, I thought it might be helpful to share this information with the community - I've been tearing my hair out about this all week.
Chrome's most recent update, to use non-technical terminology, broke the crap out of a ton of Wordpress sites and other web applications. Chrome's forcing sites to look for HTTPS when there's no HTTPS to be found, which, in some cases, prevents you from accessing your Wordpress site entirely. Here's a pretty good explanation of what's going on: https://ma.ttias.be/chrome-44-sending-https-header-by-mistake-breaking-web-applications-everywhere/
Per the article and Google's release schedule, it looks like the issue's supposed to be fixed in the next update, Monday, 27th of 2015. For our customers, we're going to ride it out and see if a fix gets implemented on schedule, but the article comments include a plugin hosted on Github that resolves the issue.
In any case, if there's anyone else going crazy trying to figure out what's going on with their sites, I hope this helps.