hidao Posted Sunday at 03:39 PM Posted Sunday at 03:39 PM 22 minutes ago, Dave-H said: Ah right, I'm still using R6. Same to you: 1
Klemper Posted Sunday at 03:57 PM Posted Sunday at 03:57 PM 12 hours ago, VistaLover said: ... Please, STOP spreading untruths! The code is there on GitHub for those willing to read it; after all, Supermium is still OPEN source (minus the wrapper DLLs, that is): https://github.com/win32ss/supermium/issues/1290#issuecomment-2764577016 @mjd79 isn't "spreading" anything . The legit sandbox question was moved to "closed" without any answer from the developer! https://github.com/win32ss/supermium/issues/1292 2
NotHereToPlayGames Posted Sunday at 04:08 PM Posted Sunday at 04:08 PM 24 minutes ago, Klemper said: without any answer from the developer! Was it answered in a previous issue tracker?
Klemper Posted Sunday at 04:24 PM Posted Sunday at 04:24 PM 11 hours ago, NotHereToPlayGames said: Was it answered in a previous issue tracker? No, and Dave'H's legit question regarding the versions is also completely ignored. I even think it's rude! Because, as we understand, the developer personally knew Dave from the days at MSFN. Dave even tagged the developer to make sure he answers, but NO answer, even though we all saw he had visited the site! https://github.com/win32ss/supermium/issues/1279 2
Dave-H Posted Sunday at 05:33 PM Posted Sunday at 05:33 PM It will be interesting to see if this is addressed in the next Supermium release. 2
NotHereToPlayGames Posted Sunday at 05:40 PM Posted Sunday at 05:40 PM (edited) 1 hour ago, Klemper said: but NO answer Yes and no. I give it the benefit of the doubt. Only the next release would indicate if the author accepted the critique or not. I don't think that the author "owes" a reply to every issue/bug being reported. I mean, there's over 500 open and 600 closed. Yes, "gigantic" bugs would be nice to have a reply. But I myself do not see them as "owed" to us. Edited Sunday at 05:41 PM by NotHereToPlayGames 1
Klemper Posted Sunday at 06:56 PM Posted Sunday at 06:56 PM Twitch and all of its functions, including subscriptions (upper right corner), work an the ancient Chrome 110 with the default flags position. And you, continue to kid yourselves further. 1
NotHereToPlayGames Posted Sunday at 07:08 PM Posted Sunday at 07:08 PM 6 minutes ago, Klemper said: continue to kid yourselves further You're not listening. Twitch this, Twitch that. Is Twitch seriously the *ONLY* web site out of roughly 1.1 BILLION of them that isn't working in Supermium? If so, that's about 438,692,547 times better than Pale Moon, Basilisk, and Serpent. I myself have never heard of Twitch until this "hit the fan". But YES, apparently it is "important enough" of a web site that the developer SHOULD BE finding out what he did to the Chromium Code that broke Twitch. 3
Dave-H Posted Sunday at 07:21 PM Posted Sunday at 07:21 PM Quite. Just because Twitch works in a Chromium 110 browser but not in Supermium 126 or 132 doesn't mean that the latter browsers are using even older Chromium versions, despite their names. There could surely be any number of reasons why Twitch doesn't work in Supermium which are nothing whatsoever to do with the underlying Chromium version. I'm sure that the reason is being investigated. The fact that it apparently comes good when the experimental features are enabled must surely be a very big clue as to the cause! 2
Saxon Posted Sunday at 07:22 PM Posted Sunday at 07:22 PM 11 hours ago, NotHereToPlayGames said: You're not listening. Twitch this, Twitch that. Is Twitch seriously the *ONLY* web site out of roughly 1.1 BILLION of them that isn't working in Supermium? If so, that's about 438,692,547 times better than Pale Moon, Basilisk, and Serpent. Twitch is an important site many youngsters use this day. The developer is still somewhat young, I don't buy it for a second he didn't check out Twitch, before the releases came out, Second, @Dave-H, there already were several releases after you found the problem in v126, but the horse is still there, and the author even introduced an odd "fix", again with "experimental features" turned on for Twitch. @NotHereToPlayGames, probably, you missed. https://github.com/win32ss/supermium/issues/1279#issuecomment-2760133080 4
Saxon Posted Sunday at 07:26 PM Posted Sunday at 07:26 PM 11 hours ago, NotHereToPlayGames said: myself have never heard of Twitch until this "hit the fan". 11 hours ago, NotHereToPlayGames said: not listening. Age, my friend, age. 11 hours ago, NotHereToPlayGames said: the developer SHOULD BE finding out what he did to the Chromium Code that broke Twitch. The developer SHOULDN'T be fiddling with Chromium Code to begin with. Just port the code, as all other forks, including CatsXP and the recently ported Chrome 136, do. 4
NotHereToPlayGames Posted Sunday at 07:46 PM Posted Sunday at 07:46 PM 8 minutes ago, Saxon said: The developer SHOULDN'T be fiddling with Chromium Code to begin with. Just port the code Agree *AND* Disagree. We still don't really know the EXACT reason that Twitch is broken. NO ONE is denying that Twitch is broken. NO ONE is trying to find another example web site! It's just "dogpile on the rabbit". If it is CSS or FONT related, then Supermium's HIGHLY APPLAUDED endeavor at attempting DirectWrite broke a CSS coding at Twitch. I don't have Twitch, I will not be signing up for Twitch. BUT IT WOULD BE NICE TO HAVE MORE EXAMPLE WEB SITES instead of just more "dogpile on the rabbit". Has anyone tried Twitch in the only other GDI/DirectWrite browser that at least I am aware of - ie, this one = https://github.com/GTANAdam/GDIChromium ? But it's also showing its age big time, it's still at v103 and appears to be an abandoned project.
Dave-H Posted Sunday at 07:59 PM Posted Sunday at 07:59 PM 31 minutes ago, Saxon said: Age, my friend, age. The developer SHOULDN'T be fiddling with Chromium Code to begin with. Just port the code, as all other forks, including CatsXP and the recently ported Chrome 136, do. Surely he had to 'fiddle' with the Chromium code or the browser wouldn't run on XP?! 3
Saxon Posted Sunday at 08:01 PM Posted Sunday at 08:01 PM 11 hours ago, NotHereToPlayGames said: v103 and appears to be an abandoned project. 103 will most likely fail on Twitch due to the fact of being too old, it even predates the official cut off point for old OS like Windows 8. So it may fail due to the old engine and simply confuse us. Any other variants? 3
Saxon Posted Sunday at 08:06 PM Posted Sunday at 08:06 PM 10 hours ago, Dave-H said: Surely he had to 'fiddle' with the Chromium code or the browser wouldn't run on XP?! As I stated above, the site rendering engine had to be left intact. It's what they do in other forks, only something that is missing is replaced, redirected. And Supermium already includes fixed DWrite.dll , so no reason to dig the sire rendering part. But I too think it's the old Chrome 109 (?) with the added new features to render some modern sites upon the old engine. 3
Recommended Posts