Skip to content

API spec is inconsistent with the the event status 'loading' #421

@HeinzBaumann

Description

@HeinzBaumann

The API specification says at in addEventListener section:

Note: The addEventListener callback shall be immediately called upon registration with the current TC data, even if the CMP status is loading and the CMP has incomplete TC Data, so that the calling script may have access to its registered listenerId. Furthermore, on every TC String change the callback shall be called unless it is removed via removeEventListener.

In the listing of the different CMP status it states:
-|-|-
'loading' | cmpStatus | DEPRECATED (this status is not distinct and will be removed in a future version)
-|-|-

Agreed that the 'loading' status may not be distinct. I don't know why we marked it DEPRECATED. So perhaps we change this description to so say: "Indicates the CMP is loading. (This status is not distinct and might be removed in a future version.)"

Metadata

Metadata

Assignees

Labels

Under ReviewIssue is getting reviewed by the MObugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions