You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Represents property is inheritable. If it is absent from an element then its computed value is the computed value of the Represents property on its parent element, or, if it has no parent element, it is the empty string. If it is present on an element then its computed value is the value specified.
Currently it is not possible that a parent element can have a @represents attribute as script events can not be nested and @represents can only be used on script events.
Note
Since there is no empty <content-descriptor>, this implies that an empty computed Represents property can never be valid; one way to construct a valid DAPT Document is to specify a Represents property on the DAPT Script so that it is inherited by all descendants that do not have a Represents property.
Only Script Represents can be specified on the DAPT Script not Represents (at least for now).
The text was updated successfully, but these errors were encountered:
a small refactor to define the inheritance on the daptm:represents attribute specifically, and note that it is permitted on <body> and <tt> as well as div OR
explicit permission to permit Represents at the Script level.
I prefer the first option because the data model doesn't include script event groups, i.e. <div> elements that are not Script Events, but that would be an obvious syntactical location for specifying an inherited daptm:represents value.
Section 4.7 states
Currently it is not possible that a parent element can have a
@represents
attribute as script events can not be nested and@represents
can only be used on script events.Only Script Represents can be specified on the DAPT Script not Represents (at least for now).
The text was updated successfully, but these errors were encountered: