The first divider line of the Chinese readme file is not rendered.

Steps to reproduce it

1. To view the readme file under https://github.com/alvarotrigo/fullPage.js, click on the "Chinese" jump to the Chinese version of the readme.
2. Under the words "for Vue, React and Angular" in the Chinese version of the readme file is the word "---" .
3. There is no component secant for this mar

你好，我是哈利。我参与为开源项目创建文档。这是我在帮助开源项目方面所做贡献的一部分。我参与创建的文档之一是隐私政策。隐私政策将提供有关用户信息收集，使用和安全性的详细信息。我真的不知道你是否从外部收集用户信息，但是，如果你不这样做，最好通过隐私政策让最终用户知道。
贡献者指南也是一份重要文件，可以帮助潜在的合作者轻松地为您的项目做出贡献。

我很想听听你对此的看法。

Hello, I'm Harry. I engage in creating documents for open source projects. It's part of my contribution in helping open source projects. One of the documents I engage in creating is a privacy policy. The priva

The <full-page> component is not replaced with <div> element in the template when running nuxt generate.

This can be replicated with a basic setup following instructions for Nuxt.js and instructions for

Hello I tried to set up FullPage.JS with Gatsby and as soon as I add an extension (Parallax or similar) I get this message every time. No matter how often I try it, or which examples I take from the docs, it just doesn't work. It would be great if someone could help me or a working example (the Gatsby link in the docs doesn't work, the one from Next.JS does). I also used the example from https://g

Expected behavior

Actual behavior

Steps to reproduce the b

The current configuration wiki provided is not complete and/or outdated. It causes confusion to me and probably many other people. Could you update it at least 1 by 1 when you have free time?

In separate issue immersive-web/dom-overlays#20, @chrishtr pointed out several issues related to the interaction of the fullscreen API and WebXR DOM Overlays, and suggested several changes to the Fullscreen API to better define the expected behavior:

@chrishtr wrote:

I researched the fullscreen and DOM overlay specs in some detail, together with @progers and @mfreed