tell me if there’s a concept of making fully-qualified names for well-known functions/constructors supported in various browsers in development? Obviously, I am not talking of .name property. I am, however, talking of a way to reconcile if this Map constructor function (in this Chrome v.X) acts the same was as that Map constructor functiuon (in that, say, Safari). Sort of scheme, namespace, or FQN - but with application to JS.
For instance, using Messaging Web API I can pass around, across js boundaries, the pieces of simple data and stringified objects and arrays. But not anything slightly more specific, like sets or maps. Even for dates, I will have to pass the dates’ representaton (either a UTC format, or timestamps along with the knowledge that this string or number represents a date). While dates are pretty common, there is a number of other types which can be recreated in certain js boundaries using correct representation strings. However, there is none widely agreed upon. Is there anybody here that understands the context I am referring to? Please kindly respond
What are you talking about
Обсуждают сегодня