Introduction of XML and difference from html

The coverage.out generated by gotest-coverprofile is plain text coverage data, which needs to be converted into HTML using gotoolcover-html before it can be visualized. Common blank spaces or jump failures are due to source code path mismatches, so the generation and viewing environment must be consistent.

text-indent only takes effect for block-level elements, inline elements need to set display:block; it may not work in flex/grid containers, it is recommended to use padding-left instead; 2em is not equal to the width of two Chinese characters, ch unit or rem is recommended to improve consistency.

Mnemonic phrase security needs to prevent five types of risks: 1. Screenshots causing leakage of photo albums and clouds; 2. Online storage being hijacked through multiple links; 3. System cache retaining copies; 4. Cloud input method uploading content; 5. Browser developer tools capturing DOM plain text.

html/template will automatically escape all {{.}} interpolation content: When using html/template, if variables are directly inserted through {{.Var}}, Go will automatically escape HTML special characters when rendering.

Inline style seriously damages the stackability, reusability and maintainability of CSS, and is only acceptable in a few scenarios such as email templates or minimalist static pages.

Notes on using golang.org/x/net/html to parse HTML in Go: skip comment nodes, only format text spaces in non-preformatted contexts, use html.Render to output to avoid self-closing tag errors, and disable compression of script style content.

The main reason why embed.FS returns fs.ErrNotExist is that the //go:embed annotation does not closely follow the embed.FS type variable declaration, the path is relative to the Go file rather than the project root directory, or the http.FS package is missing, causing http.FileServer to be unrecognizable. When reading binary resources, string conversion must be avoided, and large files should be used with caution. During the development stage, the build tag should be switched to os.DirFS to achieve hot reloading.

Tomcat is a JavaWeb server that runs independently. You need to configure the JDK correctly first (JAVA_HOME points to the JDK root directory and PATH includes bin), and then decompress it to a path without Chinese and spaces. You can modify the Connector port in conf/server.xml before starting. It is recommended to use WAR packages to deploy applications and put them in the webapps directory.