On 19 Sep 2019, at 10:23, Hussein Shafie wrote:
On 09/19/2019 09:05 AM, Leif Halvard Silli wrote:
One possible solution: What I would suggest is that @type is added
back
as one of the attributes style elements can have. However, instead of
making the @type attribute available - by default - in the attribute
edititing tool, it ought to be hidden by default. For instance, it
could
be hidden as a "scripting" attribute - meaning that users must
activate
"Show 'scripting" attribute" in order to see the "type" attribute. Or
even better: Instead of simply adding type to the "scripting"
categroy,
add a new category "obsolete but conforming" attrributes.
Given the fact that you permit @border on the table element
(something I
think is a smart decision[*]), I think you should definitelely find
some
way to add back type="text/css" as well, given the fact that it
actually
is a conforming feature.
We claimed in https://www.xmlmind.com/xmleditor/changes.html#v9.1.0:
---
XHTML5 configuration: updated our in-house XML Schema and added a
companion Schematron in order to implement most of the conformance
requirements for authors specified in the HTML Living Standard.
---
So this is really a "best effort" implementation. We certainly missed
things.
We have no problem adding back @type to <style> with "text/css" as the
only conforming value.
Good. Would it be possible to download your schema with the type@style
support pretty soon? Or, perhaps a "keep using HTML 5.*" addon (while we
wait for next release)?
Please do not hesitate to suggest changes like the above one if we
missed some points in our implementation.
I will certainly do, if I stumble upon something.
Leif
--
XMLmind XML Editor Support List
[email protected]
https://www.xmlmind.com/mailman/listinfo/xmleditor-support
