2 issues: Welcome Guide pop-up and call to fonts.googleapis.com

[wphtaccesssucks920]

Using WP latest version as of September 27 2020.

No plugins, deleted all plugins that were preinstalled with WP installation.

No themes but those default installed by WP itself.

Issues appear to be related.

ISSUE #1
when creating and/or editing a new page or post, the WelcomeGuide pop-up shows invariably. That is, it does not matter a first or the 100th page/post is created/edited.

This is annoying and time wasting.

I attempted to configure the options in WP block editor but the latest WP version does not allow to uncheck this "feature". Clicking Welcome Guide option in the Options menu only brings the Welcome Guide pop-up once more.

This needs to stop. This is a time waster and of little, if at all, value to content creators. This is unacceptable in a supposedly mature product.

This "bug" is not a new report, I've seen comments on different forums from frustrated content creators since at least 2 years ago.

This makes wordpress something I would want to avoid. And I did for the past 5 years.

ISSUE #2
The Welcome Guide pop-up/function calls for Noto serif google font. It makes a call to fonts.googleapis.com.

I blocked external calls from WP. As a result, Welcome Guide tries to download that font from its source; being blocked only delays the page for 30 seconds or so until it times out, then Welcome Guide displays just fine.

In addition to Welcome Guide being criminal (who in his/her all mental faculties would want to add such code to torture wp user base?), it actually does nothing but wastes time. And creating a potential privacy (legal?) issue.

These calls to fonts.googleapis.com need to be stopped. WP might be in conflict with GDPR in Europe, create potential legal problems to those hosting a website in WP, wastes time and slows down the site using WP.

These issues are THEME/PLUGINS independent and are coded in WP core.

[carike]

Hallo and welcome to Trac.

A few housekeeping things:

1. Please do not report multiple issues in one ticket. This is because of workflow. One distinct issue per ticket, so that that issue can be tracked as it is patched / closed / other action.

2. While I understand that you are frustrated, we do expect all contributors to be civil to each other. Please refrain from personal comments.

3. I realize that it is frustrating to be sent from here-to-there, but Gutenberg development happens on GitHub. For these issues to receive attention, you would need to create issues (separate ones, please) for them there. Here is a link to the repo: ​https://github.com/WordPress/gutenberg

[aristath]

Duplicate of #46169.

Related to https://core.trac.wordpress.org/ticket/46169
There is a discussion there on removing google-fonts, so I'll go ahead and close this one as a duplicate of that ticket.
If a decision is made to switch to core fonts (or some other laternative like locally hosting the webfonts), then it will be done on that other ticket and applied across the board - which would also fix the issue on welcome guides.