/kc/ - Krautchan Beschwerdestelle

Reportierungen, Beschwerden und Verbesserungsvorschläge: Hier hinein.

Eintragsmodus: Antworten [Zurück] [Gehe nach unten]

Betreff:
Säge:
Kommentar:
Zeichnung: x Zeichenfläche
Dateien:
Passwort: (Kommentarlöschung)
  • Erlaubte Dateitypen: GIF, JPG, PNG, NetzM, OGG, ZIP und mehr
  • Maximale Anzahl von Dateien pro Post: 4
  • Maximale Dateigröße pro Post: 100.00 MB
  • Lies die Regeln bevor du postest.

de Bernd 2025-08-26 09:02:43 9b0338 Nr. 305

Datei öffnen 5.81 KB, 222x227
Pfostenbild
There's a bug that you can't copy multiple images (clipboard images) into one post, it fails to send. You have to download the images individually and upload them like regular files.
It also seems that some images which are too big can’t be copied
>>306 Is that it? I had the impression that I couldn't paste webp, but maybe it was the size that was a problem.
>>306 That seems to be the actual error, but >>305 could not be reoroduced here.
testpfosten #2
>>306 Well, it seems the error is file size. If you copy a high resolution JPEG (or WEBP) it can become a real big bitmap file. Because of technical limitation, that clipboard images are always raw bitmaps. This could become to huge for the JavaScript to handle for compressing into PNG and also to huge to upload hitting the 100MB barrier.
>>312 Gepriesen sei das rauhe Haus.
>>311 See? I tried to copy four normally sized images and it wouldn't send the post. They're not even high resolution. Here are the image links I tried: https://i.4cdn.org/lit/1756503334985064.png https://i.4cdn.org/lit/1756410970381622.jpg https://i.4cdn.org/lit/1756107913597550.jpg https://i.4cdn.org/lit/1756491122930504.jpg
>>315 Why does it say png when 3 out of 4 are jpegs? Can you try copying 4 jpegs?
>>316 KC converts all clipboard images to png it seems
>>320 Mmh which browser are you using? Maybe it’s a me problem…
>>321 This was in Firefox under Fedora. I tried it under windows and couldn't post even with one image. Maybe this is helpful to Generalmajor: Uncaught (in promise) TypeError: SubtleCrypto.digest: Argument 2 could not be converted to any of: ArrayBufferView, ArrayBuffer. onloadend https://krautchan.org/.static/js/postCommon.js?c=1747318602816:540 newCheckExistance https://krautchan.org/.static/js/postCommon.js?c=1747318602816:534 newGetFilesToUpload https://krautchan.org/.static/js/postCommon.js?c=1747318602816:597 processFilesToPost https://krautchan.org/.static/js/thread.js?c=1747318602820:979 processReplyRequest https://krautchan.org/.static/js/thread.js?c=1747318602820:1002 checked https://krautchan.org/.static/js/thread.js?c=1747318602820:1069 handleConnectionResponse https://krautchan.org/.static/js/api.js?c=1749256797435:310 connectionStateChanged https://krautchan.org/.static/js/api.js?c=1749256797435:384 formApiRequest https://krautchan.org/.static/js/api.js?c=1749256797435:350 postReply https://krautchan.org/.static/js/thread.js?c=1747318602820:1047 postCommon.js:540:21 onloadend https://krautchan.org/.static/js/postCommon.js?c=1747318602816:540 AsyncFunctionThrow self-hosted:804 (Async: async) newCheckExistance https://krautchan.org/.static/js/postCommon.js?c=1747318602816:534 newGetFilesToUpload https://krautchan.org/.static/js/postCommon.js?c=1747318602816:597 processFilesToPost https://krautchan.org/.static/js/thread.js?c=1747318602820:979 processReplyRequest https://krautchan.org/.static/js/thread.js?c=1747318602820:1002 checked https://krautchan.org/.static/js/thread.js?c=1747318602820:1069 handleConnectionResponse https://krautchan.org/.static/js/api.js?c=1749256797435:310 connectionStateChanged https://krautchan.org/.static/js/api.js?c=1749256797435:384 (Async: EventHandlerNonNull) formApiRequest https://krautchan.org/.static/js/api.js?c=1749256797435:350 postReply https://krautchan.org/.static/js/thread.js?c=1747318602820:1047
>>324 The very same image in the very same thread worked in Fedora. Working: Firefox 141.0, Fedora 42 Not working: 142.0.1, Windows 10
>>324 In Firefox on Windows it failed, in Chrome on Windows it worked hmmm
Test
It seems under certain circumstances that the JS crashes. As for now it's difficult to reproduce. We will keep working on it an see how to fix this.