Hard to tell but Iâve seen this on various sites now and itâs always with Chrome, but other browsers are not affected. In my case I am using a fairly decent spec VPS with SSD, 5 gigs of Ram and CloudFlare Pro.
Just talking aloud here, Blocs site as the example:
My 2 cents:
Probably need a larger pool of people giving feed back, if they experience it first, butâŚ
I actually see it with the Blocs site in Chrome also (75mb connection, SSD HD, Server Grade Ram, etc.,). The odd thing is typically this is referred to as FOUC (Flash Of un-Styled Content). But I am clearly seeing styled content when it flashes on sites.
I wonder if it instead has to do with appending the âpage-loading-blocs-notifactionâ via JQuery and Chrome has a milli/second delay or something? Even if I close the page and itâs cached and then reopen it from history I see it (75mb connection, etc.,), so thatâs rather weird. I wonder if placing the âpage-loading-blocs-notifactionâ DIV directly in the page source above the "page-containerâ as part of the source and not append it via JQuery would address it. Then manage it a bit differently, hide the "page-containerâ via the CSS immediately, then when things are loaded in the .load function display it and then fadeOut, remove() the âpage-loading-blocs-notifactionâ. Just an idea. Itâs a bit weird given some of those conditions though.
Maybe itâs something to do some tests with, you probably would want/need a big pool of testers to see if it actually changes anything before taking the time to change it in Blocs however. I know Google is also big on addressing ârender blockingâ with CSS and JS, so maybe Chrome handles things differently or more rigidly also.
I wonder if we are talking at cross purposes here. I see a long delay in page opening with Chrome on most sites that use a preloader. Anywhere from 10 seconds to never. This is not just limited to Blocs sites.
If you are simply seeing a flash as the page opens it might be something like faux rendering that comes from Google fonts as the styling is applied. It could be that Chrome is treating these files differently to other browsers. I am on a Mac Pro here with SSD + 32 gigs of Ram and 76mb connection, but I donât think the computer setup has any major influence on this.
âShow moreâ options:
Iâm using âToggle Visibilityâ.
This function currently available, only the v2.3 beta
Before I created a little demo of Toggle visibility.
Uploaded the source file: http://benhodosi.com/x/
One thing I donât understand in your Toggle Visibility demo, is why there are 2 Target IDâs set in each Go to Button. E.g The Go To 2 button has the target IDâs id1, id2, Go To 3 had id2, id3, etcâŚ
@Ben Thank you this was very useful. Iâve had Blocs for a couple of weeks now but not yet had time to dive in and look at some of the real functionality.
There is a developer for Rapidweaver who always creates demo projects that highlight the features of his stacks and I think it would be really helpful if @Norm could create a library of test projects like this that demonstrate different options within Blocs. At that point when you need to learn how something works you just download the demo file.
I am trying to duplicate what youâve done on your site with the Interaction Toggle Visibility. I was able to set it up where on your site it says âShow MoreâŚâ and when I click it, it drops down the additional examples, but when I scroll down to the âShow LessâŚâ and click on it the page scrolls up exposing the lower half of my site (if the drop down height is higher then my computer screen).
My question:
When I click on the âShow LessâŚâ button, how do you get the page to scroll back up to the top of the original bloc. Seems to me if I could use the Toggle Visibility along with the Scroll to Target Iâd achieve my objective, but you can use only one interaction per selection. Does this make sense? Thanks.
After export, edited manually.
Add the following code for every row which contains âShow lessâŚâ: " onclick="scrollToTarget(â#IDxxâ)
I hope this will help.