silverfox93

Hi,

Re the help article you linked to: does the data transfer to the new custom table wp_shortpixel_postmeta happen automatically when I upgrade the plugin from version 4.22.10, or do I need to do this as a manual process after updating?

Thanks,

Thanks. I’ve completed your contact form as requested.

I tested Jetpack Boost using a default theme (Twenty Twenty) and added your Custom CSS via the WordPress Customizer and my header elements were rendered using the system font stack specified.

I think there may be some confusion here, because the headers are being rendered in the browser correctly, i.e. using the system fonts – that it not the problem. The problem is that Jetpack Boosts is adding the font-family:Lato code for headers in the critical CSS. However, that is then getting overwritten with the correct CSS as taken from the ‘Additional CSS’ section in WordPress.

Thanks. I cleared the browser cache, logged back into WordPress and then I was able to delete the form.

Hi @jpowersdev

Thanks for getting back to me.

I tried opening Chrome Developer Tools and then opened the console before deleting the form. This time the form deletion worked; however I did see this error message in the console:

A page or script is accessing at least one of navigator.userAgent, navigator.appVersion, and navigator.platform. In a future version of Chrome, the amount of information available in the User Agent string will be reduced.

To fix this issue, replace the usage of navigator.userAgent, navigator.appVersion, and navigator.platform with feature detection, progressive enhancement, or migrate to navigator.userAgentData.

Just to clarify, the CSS fix only worked for Chrome, it did not work for Safari. I will reply to your colleague via email.

• This reply was modified 3 years, 4 months ago by silverfox93.
• This reply was modified 3 years, 4 months ago by silverfox93.

Hello @belimperial,

I applied the CSS you supplied, and whilst this appears to have fixed the problem in Chrome, I’m still seeing it in Safari.

I’ve sent you a link via your contact form to a page on my site where you can see this issue for yourself.

Thanks

• This reply was modified 3 years, 4 months ago by silverfox93.

Thanks. I can confirm that version 1.1.1 has fixed the issue for me

Hello @mariatogonon

Can I email you a link to the page in question please as I’d rather not publish it on the support forum?

• This reply was modified 3 years, 4 months ago by silverfox93.

I am also having this issue. But do we have to make the above change in the accessibility settings for every pop up individually, or is there a global setting for all pop ups?

Thank you.