Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Proposed CC0 1.1 contains invalid encoding declaration #1213

Open
1 task done
Jayman2000 opened this issue Aug 1, 2021 · 1 comment
Open
1 task done

[Bug] Proposed CC0 1.1 contains invalid encoding declaration #1213

Jayman2000 opened this issue Aug 1, 2021 · 1 comment
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix 🟧 priority: high Stalls work on the project or its dependents 🚧 status: blocked Blocked & therefore, not ready for work

Comments

@Jayman2000
Copy link

Jayman2000 commented Aug 1, 2021

Description

According to the HTML Standard, a meta element can have its http-equiv attribute set to content-type. In this situation, the http-equiv attribute is in the Encoding declaration state. The proposed CC0 1.1 has an http-equiv attribute that’s in the Encoding declaration state.

<meta http-equiv="content-type" content=
  "text/html; charset=utf-8" />

According to the HTML Standard, “The Encoding declaration state may be used in HTML documents, but elements with an http-equiv attribute in that state must not be used in XML documents.” The proposed CC0 1.1 is an XML document.

Reproduction

  1. Get a copy of the proposed CC0 1.1.
  2. Change its file extension to .xht or .xhtml.
  3. Try validating it.

Expectation

The page validates successfully.

Resolution

  • I would be interested in resolving this bug.
@Jayman2000 Jayman2000 added 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🛠 goal: fix Bug fix 🟧 priority: high Stalls work on the project or its dependents labels Aug 1, 2021
@SamarthShukla17
Copy link

I would be interested in resolving this bug.

@TimidRobot TimidRobot moved this to Triage in TimidRobot Sep 10, 2024
@TimidRobot TimidRobot added 🚧 status: blocked Blocked & therefore, not ready for work and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Sep 18, 2024
@TimidRobot TimidRobot moved this from Triage to Backlog in TimidRobot Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix 🟧 priority: high Stalls work on the project or its dependents 🚧 status: blocked Blocked & therefore, not ready for work
Projects
Status: Backlog
Development

No branches or pull requests

3 participants