Benjamin Intal

I’d like to add also that the inlined CSS is produced for the changes in styles on a per-block basis. And the inlined CSS is specific to only the blocks in the current page, so the CSS is most likely not reused in other pages.

Because of this, having an inlined style tag is better than having to split it off to another remote stylesheet that your website would have to load only for that specific page – which by the way your server would have to generate this remote stylesheet whenever the CSS changes.

Hello, I do not believe this warrants a 2-star rating or lower.

Custom block attributes may produce inlined styles, when you have optimize CSS option enabled (this is enabled by default), it will combine them into one style tag. If you have a performance plugin, this can be offloaded into a separate CSS file.

We purposefully did this so that:

1. the CSS will load faster (1 less external file to load and no flash of unstyled blocks), and
2. to integrate well with performance plugins and solutions

Hey @rohan7506 v3.13.7 should have addressed this issue. Please let us know if it fixes things.

Thanks for the update, we have gotten another similar report that we currently testing a possible fix for, and I believe that might fix also the issue you are encountering. If all is okay we will release a fix for it in a day or two. Kindly wait for that update.

What version were you updating from? I believe there weren’t any changes from just the previous version on loading stylesheets.

Hello, I checked out your page and I decided to dig deeper as to why this might be happening. Would you be able to add this CSS in your Additional CSS (site-wide), this may get rid of the warning from Page Speed Insights (at least on Stackable’s carousel block):

.stk-block-carousel__slider .stk-block-column[aria-hidden="true"] .stk-link[tabindex="-1"] {
    display: none;
}

Let me know what happens.

Hey @mofojofo I believe that for Carousels, the aria-hidden="true" is placed on slides / focusable elements for slides that are out of view or hidden. This is intentional so that tabbing and other accessibility related stuff won’t be able to incorrectly get the focus when a slide is hidden. The aria-hidden changes when the carousel moves to another slide.

You should be able to safely ignore this warning.

Hey @mneroni, glad you found the issue! I’m resolving this thread now, please reopen or create another one if you need anything ??

Hey @alamiomar, we just released an update with a fix for this. Please update to v3.12.15 and try it out ??

Hey @mneroni, if you have updated WordPress, please make sure that you also have the latest Stackable version installed. Aside from that, it would also help to isolate the issue to see whether the issue is coming from Stackable, try deactivating other plugins one by one to see whether that fixes things – there’s a chance that there might be another plugin causing the issue since we haven’t gotten any similar reports to this recently.

We have some troubleshooting docs that might help out:

• https://docs.wpstackable.com/article/379-your-site-doesnt-include-support-for-this-block-error
• https://docs.wpstackable.com/article/383-im-encountering-block-errors
• https://docs.wpstackable.com/category/331-common-issues

We could also help you out if you would be able to send over some login details to our support email [email protected] so our support team can check things.. seeing the error first hand would make troubleshooting easier.

Hello @silasveta2012, where did you get this warning?

I don’t believe there is much Legacy JavaScript code in there – it’s only the bare essentials for browser compatibility which is added automatically during the build process. The warning also said that you will have 0.0kb savings if you modernize, so I think this should be okay.

Hey @alexshum939, tabs in general hide the content of the other tabs. So while this works for most types of content, there might be scenarios that it show issues especially for more dynamic content or interactive content.

Unfortunately, in these cases you would need to force the interactive content to re-initialize like what you’ve already done with recalculating positions.

• This reply was modified 10 months, 3 weeks ago by Benjamin Intal.

Hello, thanks for the report. Looks like a bug with the Freemius SDK we’re using, we’ll investigate this.

In the meantime, I found a source that says that it might have something to do with object preloading – are you using something like this in a caching solution? If you are, try disabling it and see if that fixes things.

Thanks!

Hello, I’m resolving this update now due to inactivity, please see our troubleshooting docs here:

• https://docs.wpstackable.com/article/379-your-site-doesnt-include-support-for-this-block-error
• https://docs.wpstackable.com/article/383-im-encountering-block-errors