| >> | Anonymous 24nov2025(mo)23:24 No.106998 OP P1| Weird bug on eye.swfchan.com I have this bug since recently, where the site and the flash just keeps reloading after a few seconds, after you GET (embed, adobe flash plugin). Also I'm missing the seekbar or downloads options. Anyone else got this? |
|
| >> | !///SWFAnts #ADMIN# 25nov2025(tu)10:53 No.107001 SWF P2R1| It was a cross-domain issue, does it work now? |
|
| >> | Anonymous 26nov2025(we)18:27 No.107010 OP P3R2 |
| >> | !///SWFAnts #ADMIN# 27nov2025(th)06:45 No.107019 SWF P4R3| I've turned off the script that reloads the frame if no download progression is detected and have added a message if the browser no longer supports embedding flash files. If the .swf can be embedded it should display without the iframe web page being reloaded, even if the JavaScript fails to read the percentage loaded. There could still be some cross-domain issue disallowing JS from reading properties of the embed because the .swf is on a different subdomain. If the flash does embed successfully but remains at 0% loaded (meaning JS controls won't show up) maybe you could try and see if there is a way to disable cross-domain restrictions in your browser? |
|
| >> | Anonymous 29nov2025(sa)22:01 No.107027 OP P5R4>>107019 Yeah, it appears like it's sitting on 0%, but the flash loads and plays fine now. I'll look into the cross domain setting in palemoon sometime. At first I thought something was fucked in the ad/scriptblocker, but XHR is greenlit on every domain.Well, peace out! |
|
| >> | Anonymous 30nov2025(su)19:12 No.107037 OP P6>>107019 Tried disabling CORS and preflight requests and also completely disabling the scriptblocker as well as whitelisting all domains in the flash player settings, but all to no avail unfortunately. I wouldn't know which settings could elsewhere factor into this. I assume that this would make it a browser configuration problem and that it works on your end, Ants? What do you personally use to access embed flashes live if you do so yourself? Any settings to recommend? As far as I understood completely turning off cross domain restrictions wouldn't be a great idea securitywise anyway. Also, other than some CORS updates on palemoon lately there weren't any changes in my browser config I think, so I wonder what brought this up? Https implementation? Some general fiddling with the finicky codebase? Haven't been using flash that much since /f/ dieded, so I cannot really say when this issue began... |
|
| >> | !///SWFAnts #ADMIN# 3dec2025(we)08:17 No.107052 SWF P7R5>>107037 >What do you personally use to access embed flashes live if you do so yourself? These days I just "open" the swf files in Adobe's old flash player from the site (they download to a temp location on my computer and is then loaded into the player).I've used two old Firefox versions (ESR 52 and 60.9) to confirm that the plugin functions as intended here on the board. Percentage loaded shows up and the seekbar works. But percentage and seekbar doesn't work on the page with the GET FILE button even though the flash gets embedded (http/https doesn't matter). I'll see if I can get it fixed. Maybe CloudFlare adds a header that makes the browser more cautious with iframes, the only thing that has really changed recently is CF starting to serve the web pages as well. |
|
| >> | !///SWFAnts #ADMIN# 3dec2025(we)13:18 No.107053 SWF P8| Okay everything except zoom and inspect (variable reading) should work for the flash plugin now after expanding the JavaScript message system needed to communicate with stuff inside iframes these days. Main problem was that flash doesn't let you read from different subdomains other than the same as where the flash file is hosted, unless you whitelist the exact domains inside the swf with ActionScript. So 8 days ago when I moved the html file that contains the <embed> from files3.swfchan.com to eye.swfchan.com (in a first attempt to solve the cross-domain issue without changing any JavaScript) the flash itself started refusing JavaScript to read variables from it since the swf was then on a different subdomain compared to the html. It was the reason the <embed> was put inside an iframe years ago but I had forgotten about it. |
|