0 users browsing Discussion. | 2 guests | 2 bots  
    Main » Discussion » Mozilla, *sigh*
    Pages: First Previous 22 23 24 25 26 27 28 29 30 31 Next Last
    Posted on 21-01-24, 16:58 (revision 5)
    Dinosaur

    Post: #893 of 1290
    Since: 10-30-18

    Last post: 20 days
    Last view: 7 hours
    For those out there that don't get what is this "Web Components" thing, here is a quick introduction detailing all you need to know about this new shiny hotness:
    https://www.soubai.me/post/whats-the-heck-is-web-components
    Wikipedia page is quite barebones: https://en.wikipedia.org/wiki/Web_Components

    Basically it allows webshits webdevs to define custom HTML tags client-side, unlike the usual (and IMHO proper) way to do it, that is, server-side (relying on your framework to generate the corresponding HTML: a good example is JavaServer Faces custom components). It also allows the dev to define templates you can use at runtime (again: something every half-decent server-side framework had for decades). Oh, and it relies heavily on client-side JavaScript to do the Magic™, because that's the only language that matters in the web community these days.

    Custom client-side HTML tags components aren't even new: Microsoft has prior art on this, but of course that went nowhere as it dates back to the dark ages of the Trident monoculture (IE5.5!). Years later, Mozilla tried it with XBL and failed. But they say the third attempt is the good one, and we can thanks this asshole to introduce his version of what we know today as Web Components. Google liked it so much they started investing heavily on it (Polymer being the first popular implementation), and suddenly when Chrome became the new IE, they also forced the W3C to bake Web Components into the (already extremely bloated) standards. But Google WebComponents™® didn't became widespread until the last 2 years, where nearly every webdev under the sun wents pants-on retarded in their dumb chase for shiny. Welcome to the new "server-side", where your computing device is treated as an extension of Someone Else's Backend!

    Yes, I'm well aware that the workaround for non-WC-capable browsers is to include MOAR JAVASCRIPT!!!!11!!! the relevant polyfills on demand, but since webshits now assume everybody runs Chrome, noone bothers doing that anymore (because users like me don't exist). This is why GiggityHub breaks horrendously on SeaMonkey and Pale Moon, and what that addon does is to forcefully include the required polyfills to make the thing work, but that only fixes ONE website, while the rest of the Internet is now broken for those that decided not to follow the Way of Chrome (oh, and it also breaks your screen readers! Because blind people doesn't exist either). Embrace, Extend, Extinguish at its finest... and this time we can't even blame Microsoft!

    tl;dr: Google WebComponents™® exists because modern webdevs are lazy morons that don't really know what a "server" is anymore :/

    UPDATE: I now died inside after reading this repository.
    "YO DAWG I herd u liek components so we put web components on your custom components so u can haz components everywhere!"
    WHYYYYYYYYYYY?!?!?!?!

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 21-02-17, 01:06 (revision 4)
    Dinosaur

    Post: #905 of 1290
    Since: 10-30-18

    Last post: 20 days
    Last view: 7 hours
    News from Team Seamonkey:

    - NPAPI is dead, buried, and starting with 2.53.7, gone for good. Let's hold a minute of silence for the fallen souls in the quest for enhancing the web experience... enough. If your organization is dumb enough to still rely on Java applets or Flash content for its internal appliances, get your favorite weapon and start leisurely "upgrading" hardware!

    - There have been a few, very annoying instances of severe CPU hogging on the 2.53.x line. In my case, I've been bitten by two of them: one that specifically affect MercadoLibre product listings (but nothing else on their bloated mess of webshit) but which goes away after closing the tab (it even happens in safe mode on a clean profile!)... and another one hitting the "Socket Thread" subprocess - this one is nasty as it happens at random, and it even causes the entire process to stay there eating a entire core even after closing all windows, requiring to bring in the SIGTERM/SIGKILL troops. These have been a PITA to debug (I've been helping the guys at #seamonkey with straces and countless experiments... and still going!), but it seems these flaws may even come from upstream Firefox. There are no clear clues on this yet, aside of some timers suddenly missing their deadlines and therefore becoming infinite, which often leads to CPU hogs.

    - Google started today treating Seamonkey as a cellphone: the search pages turned out from desktop to mobile view across my entire Seamonkey fleet, with no way out to even tell them nicely that these are NOT cellphones! Apparently, either Google is punishing me for disabling Javascript (which actually I haven't done!), or I just became a victim of their stupid A/B experiments. So far, the only effective workaround I've found is to spoof my user agent as recent Firefox to regain the desktop view. So yeah, time to burn down Silly Valley. Nope, I'm not switching to DDG or whatever nerd-friendly search engine is in vogue these days - as much as evil has Google became, their search engine is still the best in town, sadly.
    UPDATE: Here are the magic strings to please Google... for now (yes, this shit is not new and will keep pestering you when you least expect it!):
    general.useragent.override.google.com = Mozilla/5.0 (Windows NT 6.1; WOW64; rv:61.0) Gecko/20100101 Firefox/61.0
    // or for Linux: Mozilla/5.0 (X11; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0

    That is, take your current Seamonkey user agent string as the base, bump the reported Firefox version just a bit (SM 2.53 = FF 60), and get rid of the Seamonkey token, just in case.
    But the real solution is to just embrace Google Chrome as your One True Browser™, of fucking course!

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 21-02-27, 03:10 (revision 1)
    Dinosaur

    Post: #907 of 1290
    Since: 10-30-18

    Last post: 20 days
    Last view: 7 hours
    "Remain Calm: the fox is still in the Firefox logo"

    While stupid memes are stupid (and another reason of why places like Twitter and Reddit are among the biggest mistakes of mankind), who is fool enough to still trust in Mozilla's PR machine these days?
    Firefox is NOT a brand, it's a browser, FFS!!!

    Enjoy your fox while it lasts, because one day you will wake up and it will be no more, no matter the underlying reason.

    Speaking about stupid memes... oh Mozilla, you didn't?! Why yes, you DID IT!!
    (spoilers: look at the logo)

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 21-02-27, 04:51
    Custom title here

    Post: #985 of 1155
    Since: 10-30-18

    Last post: 20 days
    Last view: 2 days
    Posted by tomman


    Speaking about stupid memes... oh Mozilla, you didn't?! Why yes, you DID IT!!
    (spoilers: look at the logo)
    Oh, hey! Nightly's got a clean-burning blue flame now instead of the old sooty orange! Such efficiency, much wow!

    --- In UTF-16, where available. ---
    Posted on 21-03-16, 15:32
    Dinosaur

    Post: #917 of 1290
    Since: 10-30-18

    Last post: 20 days
    Last view: 7 hours
    Chasing for that MercadoLibre CPU hog on Seamonkey has been one of the weirdest experiences in my personal life.

    Thanks to the help of a SM contributor (buc), we've been trying pretty much everything but the kitchen sink:
    - Clean profiles, to rule off the usual addon tampering
    - Checking on old upstream FF versions (the hog does not happen at all on <=FF54 or >=FF57, very hard to reproduce on FF55, easily reproducible on FF56 on which SM2.53 is based off... but only with e10s off!)
    - Trying with countless obscure preferences
    - Using specially hacked builds of various components, including a custom debug build of Firefox made off the SM source tree (yes, you can build vanilla FF from an ordinary SM tree) - this explains why they don't distribute symbols for the official release builds (libxul.so on this one is over 1GiB!!! Attaching GDB to it for taking stacktraces requires some muscle)
    - Disabling JavaScript: we got our first clue there, as turning off JS made the hog go away... and of course, it broke the entire site. And half of the Internet because JS is the new cross-platform language of choice :/
    - Testing launching the page from the urlbar, via commandline (I got interesting results there), and combinations of those (on FF the hog never happens if you launch the page via commandline, for whatever screwy reason)
    - Saving the page, then load that
    - Start dropping random HTML/JS snippets from the saved page. Our second powerful clue popped up here: near the end of the page, there is a rather huge ~100KiB blob of raw JSON which is basically a duplicate of the page contents, because MercadoLibre coders are a bunch of stupid monkeys. That unhealthy blob of JSON was triggering the hogs somehow!
    - Once I relayed all that info to buc, he also discovered that if you scroll to the page footer, the hog went away. Yup, that simple: scroll away until the pain reliefs!
    - He also figured out that disabling Chatzilla and using some userChrome.css hax for messing with the throbber unveiled some possible obscure bug soup that led to hogs like the MercadoLibre case. Yes, hacking the throbber graphic (which is some ancient animated GIF) made a positive impact on browser performance. WTF. Oh, that means double WTF for me as I have removed the throbber from my customized classic FF UI, yet changing the (still hidden) throbber nuked the hogs for good.


    There is still not an official cause established, much less an integrated fix, but at least I now have a set of reliable workarounds (scroll fast, or userChrome.css hax) to stop turning my poorly-cooled laptop into a furnace, because modern webdevs are a bunch of incompetent "ooooh shiny Macs!" morons :/


    In other news, have some AssholeMoon drama for today, involving our dear Seamonkey:
    https://forum.palemoon.org/viewtopic.php?f=62&t=26341
    Wonder if Tobin will even learn the very valuable skill of "put the keyboard away"... Nah.

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 21-03-30, 15:34
    Dinosaur

    Post: #924 of 1290
    Since: 10-30-18

    Last post: 20 days
    Last view: 7 hours
    Seamonkey 2.53.7 is shipping NOW, go go go~!

    (My MercadoLibre CPU hog was finally fixed... for 2.53.8 - it was real tough to debug, but it all boils down to some legacy code involving the throbber among other things, that gets heavily triggered by MercadoLibre's very broken Javascript shitsalad)

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 21-04-01, 02:14 (revision 3)
    Dinosaur

    Post: #926 of 1290
    Since: 10-30-18

    Last post: 20 days
    Last view: 7 hours
    MonkeyFix got badly borked under SM2.53.7:
    https://pastebin.com/r6hD5Bud

    The first one we're getting is due to deprecated Javascript for-each loop syntax that was supposed to be removed long time ago, but somehow it had survived all these years on Seamonkey. The fix is very simple: unpack the addon, edit chrome/mfix/content/modules/miscUtils.jsm to drop the now-useless "each" (there are two instances on that file), repack, reinstall addon, go.

    But... this only hides the fact quite some UI functionality provided by the addon is now broken: the addon silently complains about being unable to apply some very important UI tweaks:
    https://pastebin.com/iQPt1rSQ

    For those... I've got no fix yet, as I'm not very knowledgeable on Mozilla Suite internals, and MonkeyFix has been largely abandoned upstream :/ the fix is pretty easy: rewrite both "for each (var something in aCollection)" loops to "for (var something of aCollection)" form, that is, drop the "each" and change "in" to "of", otherwise you will get undefined variables instead of actual CSS stuff instances. Yay JavaScript.

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 21-04-01, 05:36 (revision 1)

    Post: #326 of 451
    Since: 10-29-18

    Last post: 23 days
    Last view: 2 days
    Since Firefox 86 (i.e. last week of February), support for going to the previous site/page via backspace key was removed. You can re-enable it in about:config by setting browser.backspace_action to 0.

    For me this is a breaking change because I regularly need to quickly traverse HTML documents at work, which works best with one hand on the mouse and one hand pressing the backspace key; Alt+Left requires two hands. (The extra keys on my mouse are already bound to other actions.)

    Subsequent data showed that the Backspace key is, by far, the most pressed keyboard shortcut inside the Firefox user interface, with 40 million monthly active users pressing the key and triggering a "Back" navigation. To put it in perspective, this was well above the 16 million Firefox users pressing the CTRL+F shortcut to search content inside a page and 15 million Firefox users who pressed the page reload shortcuts (F5 and CTRL+R).

    This giant difference between the first and other popular shortcuts led Mozilla engineers to conclude that many of the Backspace key presses were most likely accidental — with users pressing the key thinking the cursor was focused inside a form or search field, but accidentally navigating back a page, most likely also losing form data as a result.


    My current setup: Super Famicom ("2/1/3" SNS-CPU-1CHIP-02) → SCART → OSSC → StarTech USB3HDCAP → AmaRecTV 3.10
    Posted on 21-04-01, 12:52 (revision 1)
    Post: #394 of 426
    Since: 10-30-18

    Last post: 319 days
    Last view: 14 days
    What keyboard are you using that doesn't have an Alt key to the right of spacebar?

    AMD Ryzen 3700X | MSI Gamer Geforce 1070Ti 8GB | 16GB 3600MHz DDR4 RAM | ASUS Crosshair VIII Hero (WiFi) Motherboard | Windows 10 x64
    Posted on 21-04-01, 13:23

    Post: #327 of 451
    Since: 10-29-18

    Last post: 23 days
    Last view: 2 days
    https://en.wikipedia.org/wiki/German_keyboard_layout

    AltGr + Cursor Left doesn't work.

    My current setup: Super Famicom ("2/1/3" SNS-CPU-1CHIP-02) → SCART → OSSC → StarTech USB3HDCAP → AmaRecTV 3.10
    Posted on 21-04-01, 14:44
    Dinosaur

    Post: #927 of 1290
    Since: 10-30-18

    Last post: 20 days
    Last view: 7 hours
    "That's the most used keyboard shortcut, therefore our users HAVE to be morons so it has to be removed!"

    Flawless logic! That's Moz://a hard at work, they know better than you on how to use your own devices.

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 21-04-21, 11:44 (revision 1)
    Dinosaur

    Post: #935 of 1290
    Since: 10-30-18

    Last post: 20 days
    Last view: 7 hours
    Your monthly news recap from Planet Mozilla:

    - Seamonkey 2.53.7 shipped not long ago... and broke some old addons due to long-deprecated Javascript junk. Since getting upstream to fix their shit is simply not happening (as said addons have been largely abandoned and nobody is willing to fork them, at least), the SM team had to release 2.53.7.1, reverting said removals (actually these were hidden behind a compile-time flag).

    - Still with Seamonkey, random CPU hogs out of the blue are still a PITA. This time I've got a new one, and we can blame GiggityHub for that: remember we now need an stupid addon just to unfuck GH on our non-Google WebComponents®-enabled browsers? Unfortunately using said addon can lead to singlecore CPU hogs on both SM and AssholeMoon, and the cause is not clear yet. This is yet another difficult issue to debug, as I've failed to recreate it on a clean profile, but on a exact clone on another, older PC, it happens reliably when you unplug the network cable (!!!), or otherwise disable the network connection! (Socket Thread goes berserk, and users end with toasty laptops and sluggish performance). If you disable the addon, none of this happens... and GH remains unusable because they don't give a fuck, even if you host your non-Chromified browser sourcecode there. Sadly, getting devs to stop using GiggityHub is like getting people IRL to respect social distancing to not die of the China Pest, in other words, it's not happening anytime soon :/

    - Google Drive is now unusable on SM, if you want to actually share the stuff you upload there with others: the "get link" dialog now comes up invisible, due to some CSS fuckery I can't figure out yet.

    - Back to The Chromification of Moz://a, the UXtarded art school dropouts continue doing pointless tweaks to wreck whatever remains from the Firefox UI. Firefox 89 will suck harder, yay!

    - As for AssholeMoon, it's still run by very toxic assholes (that would prefer that nobody ever played with its sourcecode), and it's still a thing. Unless you're on Mac, where it's no longer an option. There is now an active fork for keeping the Mac version alive, despite the wishes of Manchild and Matthole Tobin to "not waste time on a mostly dead platform". I must give credit when due, even if it is to self-evident morons: Macs are about to become more irrelevant than ever (outside the SV techbro bubble which still orgasms every time the M1 is mentioned in the news) since the transition to ARMacs - the day Apple sells the last x86 Mac, it's over for most FOSS enthusiasts - remember, Apple machines are now appliances, not PCs!

    - Oh, but at least their Supreme Leader and Asshole-in-Chief are letting a new FreeBSD port survive... for now. There is still some friction between both sides, but it seems Manchild needs to gain back the users he is about to lose due to the death of the Mac version.

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 21-05-05, 11:10
    Dinosaur

    Post: #939 of 1290
    Since: 10-30-18

    Last post: 20 days
    Last view: 7 hours
    After several gigabytes (!!!) of debug traces and logfiles, and managing other impacted users to find reliable ways to trigger the hog, the "Giggityhub unfucker addon" hog has been finally found and fixed on Seamonkey (and incidentally, Pale Moon too):
    https://github.com/JustOff/github-wc-polyfill/issues/10#issuecomment-826152684


    Turns out the extension has been innocent all these months, and the real cause was that anything using WebSockets could trigger the hog, due to some code that Mozilla never bothered testing with e10s off (as it happens on Gecko forks/derivatives like SM/PM). Hell, even unplugging/replugging the network cable would cause Socket Thread to go into brain-eating zombie mode!


    Anyway, now the cause is understood, patches are available and are already merged on the relevant upstream projects, and there is a workaround you can use if you can't wait for the patch ("network.notify.changed" = false).

    NEXT!

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 21-05-05, 11:19
    Ties the room together

    Post: #551 of 599
    Since: 10-29-18

    Last post: 16 days
    Last view: 1 hour
    Yaaaaaaay!
    Posted on 21-05-05, 11:25
    Dinosaur

    Post: #940 of 1290
    Since: 10-30-18

    Last post: 20 days
    Last view: 7 hours
    Relevant Bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1633339

    If you need to trace annoying CPU hogs on Seamonkey, buc is your man. He will make you do BORING tests (including completely irrelevant stuff... or is it?), until eventually figuring out the root of the problem!

    (I even got mentioned on a recent Status Meeting for helping, yay~! - turns that it does pay out to get involved, even if you can't C++. Once again, Team Seamonkey needs your help~!)

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 21-06-05, 20:09
    Dinosaur

    Post: #952 of 1290
    Since: 10-30-18

    Last post: 20 days
    Last view: 7 hours
    Another day, another shipwreck by the Highly Paid UXtarded art school dropouts at Moz://a.

    They changed the UI. AGAIN. Workflows were broken, eyesights were impaired, threats to defect to Googleborg were issued, etc. In the meanwhile, if you still must use Firefucked for whatever reason, disable Proton with browser.proton.enabled = false, but remember, it's a pref for advanced users only, and since Moz://a doesn't want advanced users anymore, said pref will be gone for the next major release. Hope you love taskbar-shaped tabs.

    I'm growing too old for this shit, guys.

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 21-06-05, 23:17

    Post: #346 of 451
    Since: 10-29-18

    Last post: 23 days
    Last view: 2 days
    Concerns were raised months ago, but...

    (Tabs still look the same in Tree Style Tab, btw.)

    My current setup: Super Famicom ("2/1/3" SNS-CPU-1CHIP-02) → SCART → OSSC → StarTech USB3HDCAP → AmaRecTV 3.10
    Posted on 21-06-14, 22:44 (revision 2)
    Dinosaur

    Post: #956 of 1290
    Since: 10-30-18

    Last post: 20 days
    Last view: 7 hours
    The latest forge to embrace the Google WebComponents® craze: Gitlab.

    Starting today (?) their entire site is broken for us Seamonkey users because they deployed some Google WebComponents®-enabled third party lib update. Now I can't:

    - browse files
    - view files
    - search for issues
    - use their editors
    - do anything at all with their bloaty site

    Welcome to the SHITLIST, GiggityLab!

    UPDATE: also broken on Waterfox Classic (and most likely in The Browser That Shall Not Be Named). One of the SM leads even chimed in for all of us:
    https://gitlab.com/gitlab-org/gitlab/-/issues/333598
    24 hours later there is still no reply (not even a "CLOSED WONTFIX INSTALLCHROME HEALTHYECOSYSTEM NOLONGERWELCOMEHERE"!), just as expected.

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 21-07-01, 23:38
    Dinosaur

    Post: #959 of 1290
    Since: 10-30-18

    Last post: 20 days
    Last view: 7 hours
    JustOff's GiggityHub unfucker addon added support for GiggityLab, and only because the Seamonkey devs are trapped there :/

    But in less miserable news, Seamonkey 2.53.8 just shipped yesterday, so GO GO GO!

    ...unless you use email, in which case you might want to hold a bit for 2.53.8.1.

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 21-07-08, 01:19 (revision 2)
    Dinosaur

    Post: #964 of 1290
    Since: 10-30-18

    Last post: 20 days
    Last view: 7 hours
    https://github.com/SteamDatabase/steamdb.info-issues/issues/718

    ...

    THERE IS STILL HOPE IN MANKIND!?

    My legit bugreport didn't got inmediately dismissed with a routine "use Chrome/latest Firefux or GTFO", instead it got a quick fix. Live, into the production site, in just a few minutes. Please tell me I'm dead and the universe just imploded, pretty please?

    Ah no, I'm alive, and for the first time ever, I feel respected and appreciated as an user! (Sure, I also got the not-so-routine "Seamonkey devs should get its game together and update" instead, but hey, I'll take whatever I can get!)

    Plenty of webshit is breaking left and right on Seamonkey due to all those new shiny additions to one of the worst programming languages ever (nope, that's not PHP. Not anymore!). The solution? Backport piles and piles of code from later Firefox releases. Fun. Unfortunately I can see the remaining SM devs feeling the burnout, as dealing with this gargantuan task is a nightmare of epic proportions... and all for what, for a never ending game of chasing shiny because Google and Silly Valley!?

    Fuck, we now have websites implementing IE-specific bugs in 2021. Case in point: Western Digital's warranty checker, which is now broken on Seamonkey because recent Firefox releases finally caved to implementing a very IEsque bug from 18 years ago, and of course the webshits at WD just had to have fun with it. Ah well, another reason to NOT buy anything from those dicks - their products suck anyway :/ Oh, and implementing THAT specific behavior on Seamonkey (which also affects other browsers, and it's a bug that you should NOT rely on, unless you're a webshit!) most likely WILL break addons. What the hell is wrong with webdevs nowadays!?!??!?!?!

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Pages: First Previous 22 23 24 25 26 27 28 29 30 31 Next Last
      Main » Discussion » Mozilla, *sigh*
      Yes, it's an ad.