Closed johnfoliot closed 3 years ago
Example in question:
Thanks Chalres,
Yes, this is coded to look like an element as opposed to an attribute:
It should likely look like this: or <div
aui-distraction="moving ad">
JF
On Mon, Mar 12, 2018 at 1:47 PM, Charles LaPierre notifications@github.com wrote:
Example in question:
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/w3c/personalization-semantics/issues/46#issuecomment-372401909, or mute the thread https://github.com/notifications/unsubscribe-auth/ABK-c-CpbsfBBtFWHFSR-oWLvegmCaJBks5tdrTEgaJpZM4SPgYf .
-- John Foliot Principal Accessibility Strategist Deque Systems Inc. john.foliot@deque.com
Advancing the mission of digital accessibility and inclusion
I agree we should be clear and that our "list" of values should be "space separated list" of values
This is where Token List is defined https://www.w3.org/TR/personalization-semantics-1.0/#valuetype_token_list
John I think we solved this. let us know if it is still a problem
It is unclear in either of the "Description" or "Supported Values" sections that the intent here is that the attribute can support a space-separated list of values, although the example appears to demonstrate that fact.
Recommend a clearer explanation of this in the spec.