Can we count on text marking objects to stay persistent as the editor is being used? Can we, in particular, add payloads to those objects and expect to get them back when invoking marking-retrieval methods?
It sounds risky to put payloads directly on the marking object without some standardized property to house the payload; we may inadvertently overwrite undocumented internal properties. Can we standardize a way to put payloads in markings?
At a minimum, assuming we are allowed to use such payloads, can we document the persistence of the text markings to solidify this feature?