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
Hi,
I've spotted a problem with Microsoft Teams images, see here. Practically, using the Team program "COPY" menu on a image, a long single-line string is copied in the clipboard (an <img src="data:image/png;base64> tag). This is not a problem with other programs like MSWORD, that recognize it as an image.
But on Dokuwiki, this append a long unmanageable string on the page. The page is no longer rendered and gives errors until you manually restore it at the Operating System level.
I think that at least the plugin should check that it's a real image before pasting it.
The text was updated successfully, but these errors were encountered:
Ahh you gotta love Microsoft. You can always rely on them to invent some non-standard bullshit to make developer's live miserable. As you can see from the linked thread this is not correct behavior on MS Teams' side.
Detecting data URLs in the pasted content shouldn't be too hard. Feel free to hire us at [email protected] if you want this implemented.
Nope, I'm not a big fan of M$ - but I have to work with their products.
There is a simple workaround (take a screenshot or also past it on Word before), but it generates unmanageable pages if you don't know it - or forget it in my case ;-(
Hi,
I've spotted a problem with Microsoft Teams images, see here. Practically, using the Team program "COPY" menu on a image, a long single-line string is copied in the clipboard (an <img src="data:image/png;base64> tag). This is not a problem with other programs like MSWORD, that recognize it as an image.
But on Dokuwiki, this append a long unmanageable string on the page. The page is no longer rendered and gives errors until you manually restore it at the Operating System level.
I think that at least the plugin should check that it's a real image before pasting it.
The text was updated successfully, but these errors were encountered: