02:53:44 <Genaker> guys i need help
02:53:54 <Genaker> the latest version aint working for me
02:54:17 <Genaker> my os is mac os x 10.9.5
03:22:53 <november> What kind of ain't working?
04:52:19 <Genaker> not launching
04:52:22 <Genaker> at all
04:52:39 <Genaker> gives me a -10810 error when i launch it from terminal
04:53:23 <Genaker> and when i launch the binary directly, it gives me "XPCOMGlueLoad error for file /Applications/SeaMonkey.app/Contents/MacOS/XUL:
04:53:25 <Genaker> dlopen(/Applications/SeaMonkey.app/Contents/MacOS/XUL, 265): Symbol not found: ___NSDictionary0__
04:53:26 <Genaker>   Referenced from: /Applications/SeaMonkey.app/Contents/MacOS/XUL
04:53:27 <Genaker>   Expected in: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
04:53:29 <Genaker>  in /Applications/SeaMonkey.app/Contents/MacOS/XUL
04:53:30 <Genaker> Couldn't load XPCOM."
04:53:44 <Genaker> so i have no idea whats wrong
04:54:21 <Genaker> maybe it needs to be compiled from source ON 10.9, but the previous version works fine
04:54:25 <Genaker> so i really dont know
05:03:36 <oneforall2> IanN_Away it used to work in ff till last 2 upgrades
05:06:11 <oneforall2> still works in konqueror,falkon even the cell ph.
05:07:13 <oneforall2> and the cell ph has ff
05:42:50 <Genaker> im back
05:42:52 <Genaker> ffs
05:43:03 <Genaker> seamonkey 2.53.15 still doesnt work
05:43:31 <Genaker> 2.15.16b1 gives me an unsupported OS error.
05:43:50 <Genaker> *2.53.16b1
10:51:34 <stefano_> hi, I did a upgrade to the last SeaMonkey version (2.53.15) and Facebook do not work any more, if I try to view Facebook's page the sete reply with:
10:51:35 <stefano_> Your request cannot be processed
10:51:37 <stefano_> A problem has occurred with your request. We will try to solve it as soon as possible.
10:51:38 <stefano_> Back to home
10:51:40 <stefano_> It's a reported behaviour?
11:20:54 <frg_Away> stefano_ you can't win with ua sniffing: http://forums.mozillazine.org/viewtopic.php?f=40&t=3106089
12:22:18 <njsg> 0121|19:42:39 <+tomman> who's asking for thinner laptops?!?!?!?!? <-- there has to be a way for laptops to compete in the swiss-army knife business, that can't happen if they're not thin enough to be usable as knives
13:02:00 <tomman> Oh, finally found an addon that broke: Flashblock is no longer blocking videos :/
13:02:19 <tomman> time to dig up why (and hopefully, fix it!)
13:04:26 <tomman> (yeah, that now means I'm vulnerable to wasting bandwidth and autoplaying video crapola, including... JWZ's blog)
13:04:55 <tomman> speaking of that guy: https://www.jwz.org/blog/2023/01/mozilla-orgs-25th-anniversary/
13:05:10 <tomman> happy b'day, Mozilla! Too sad you're dying :/
13:15:03 <stefano_> @frg_Away thank you I did the first suggested workaround and it's work again
18:04:56 <Genaker> why does 2.57 work for me
18:05:07 <Genaker> but not the latest stable?
19:19:53 <tomman> time to look why Flashblock died
19:19:55 <tomman> "Replace obsolete GetStringBundleService call in SeaMonkey bug 1794400."
19:20:40 <tomman> could be this?
19:20:42 <tomman> <stringbundle id="bundle_flashblock"
19:20:57 <tomman> var flashblockBundle = document.getElementById("bundle_flashblock");
19:23:15 <tomman> nothing useful on the error console
19:29:57 <tomman> oh, found something!
19:30:48 <tomman> Error: TypeError: flashblockEvent.getPreventDefault is not a function
19:30:49 <tomman> Archivo fuente: chrome://flashblock/content/videoblock.xml
19:30:51 <tomman> Línea: 95
19:32:26 <tomman> it's right on the function that verifies if the site is whitelisted
19:34:07 <tomman> bug #707677
19:35:25 <frg_Away> tomman rings a bell. Let me check
19:35:56 <tomman> getPreventDefault() has been deprecated for years, it seems - we should be using defaultPrevented instead
19:36:31 <tomman> found a few instances on Flashblock's XML bindings
19:37:25 <frg_Away> tomman this is super ancient. Bug 691151
19:37:36 <frg_Away> This is not standard and has a standard alternative (defaultPrevented property).
19:38:07 <frg_Away> https://hg.mozilla.org/mozilla-central/rev/ccc5f03e6dd2
19:39:03 <tomman> should be an easy fix then, time for testing
19:39:56 <frg_Away> tomman well canÄt say I am happy with breakage but it is hard enough backporting without the baggage and keep at least a default level of compatibility.
19:40:30 <tomman> yup, indeed that fixes it!
19:40:57 <tomman> frg_Away: can't be surprised anyway, considering that Flashblock has been abandoned upstream for almost 10 years!
19:41:12 <frg_Away> yeahh
19:41:59 <tomman> but hey, at least it now gets to live for another day~
19:42:11 <tomman> I had forgot how terrible is the abuse of autoplaying video
19:44:07 <frg_Away> tomman I am keeping media.autoplay.enabled alive. Has been mutilated and baically removed by mozilla in later releases. Now some mumbo jumbo like in chrome where it autoplays if you just did it in the past based on obscure user input on the site.
19:44:20 <frg_Away> ^basically removed
20:00:09 <tomman> frg_Away: the problem is that media.autoplay.enabled is not enough
20:00:16 <tomman> sites will still load the video
20:00:39 <tomman> in my case bandwidth is scarce (and sometimes even metered, for example when my DSL dies and I'm forced to fallback to spotty 4G)
20:00:57 <tomman> Flashblock blocks video completely, not a single byte will load unless I tell it so
20:01:06 <frg_Away> tomman you can block media with uBlock which I do. Everything > xxx bytes is blocked.
20:01:11 <tomman> (I'm sure adblockers achieve the same, but I don't want full-fat Ublock)
21:10:25 <frg_Away> Genaker try the latest WG9s 2.53.16b1 pre build. if it does not work it is possibly end of the line for 10.9 becuase we needed to switch to a later macOS sdk.