[Bug] Typo in schema. Incorrect `xml="lang"` attribute added to all elements
See original GitHub issueThere’s a bug in Schema, ie. typo:
if (type != "html5-strict") { globalAttributes.push("xml:lang"); ...
it should be:
if (type != "html5-strict") { globalAttributes.push("xml::lang"); ...
notice two colons instead of one
The typo forces xml attribute to have lang value (according to doc & checked in runtime). This is obviously bad thing.
Note: similar case may be the case for xml:space
however I have not checked that.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Add xml:lang attribute to multiples files at once
Hi, Is there any way that I can add the xml:lang attribute to a whole bunch of DITA files at once? As an...
Read more >W3C XML Schema Definition Language (XSD) 1.1 Part 1
The purpose of an XSD schema is to define and describe a class of XML documents by using schema components to constrain and...
Read more >Interactive Data Public Test Suite 1 Goals - SEC.gov
1 Goals. The purpose of the public test suite is to assist developers of software that must validate Interactive Data prior to its...
Read more >xml schema against XML error - Stack Overflow
Elements may have simple types or complex types. An element with a simple type is nothing much more than a wrapper around a...
Read more >9 Release Notes - Ecological Metadata Language (EML)
The top-level EML element may include an xml:lang attribute which will apply to ... This release addresses bugs which caused the schema to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
4.7.2
I’m going to close this, because as noted above the fix/feature to escape a colon was released in TinyMCE 4.7.2.