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
As browsers roll out implementation, websites will find themselves in a situation where they may want the user to paste certain data types (e.g. a specific image format). At the moment, there is no way to distinguish the following:
The browser doesn't support the format for reading.
The clipboard didn't contain the format.
If we provide an API for the website to check if a read type is supported, this would allow them to distinguish. However, we could make it easier for sites to detect this situation and/or provide error messages if they can tell whether there was a format on the clipboard that was not available to paste. ("It seems you tried to paste JPEG, but your browser only supports PNG right now.")
If reporting on arbitrary formats is not a great idea, then it could be restricted to the formats in the API.
I don't actually think this is a great idea, but I thought I'd file it as an alternative to #67.
The text was updated successfully, but these errors were encountered:
I found the list to be fairly limited also... want to support more than just images.
how about something more custom like vnd? application/vnd.xxxxxx that is specific to your own application?
As browsers roll out implementation, websites will find themselves in a situation where they may want the user to paste certain data types (e.g. a specific image format). At the moment, there is no way to distinguish the following:
If we provide an API for the website to check if a read type is supported, this would allow them to distinguish. However, we could make it easier for sites to detect this situation and/or provide error messages if they can tell whether there was a format on the clipboard that was not available to paste. ("It seems you tried to paste JPEG, but your browser only supports PNG right now.")
If reporting on arbitrary formats is not a great idea, then it could be restricted to the formats in the API.
I don't actually think this is a great idea, but I thought I'd file it as an alternative to #67.
The text was updated successfully, but these errors were encountered: