-
tomman
OK, this is getting bizarro
-
tomman
started over with a COMPLETELY CLEAN search providers file: nuked searchproviders/, search.json.*, and any backup I could find
-
tomman
added my providers again
-
tomman
and... AGAIN, Yahoo AR is replacing Wikipedia EN JUST BECAUSE!
-
tomman
will update my other amd64 laptop to 2.53.17 and try with a clean profile there
-
IsambardPrince
Is there any realistic change of seeing a SeaMonkey "Quantum" in the future?
-
tomman
lolno :P
-
IsambardPrince
I ask because I'm not certain how feasible it is to keep backporting "select patches" from Firefox.
-
IsambardPrince
Typically this gets difficult the further along something you forked from goes.
-
IsambardPrince
[Friday 7:05:05pm] tomman and... AGAIN, Yahoo AR is replacing Wikipedia EN JUST BECAUSE!
-
IsambardPrince
Yahell still exists?
-
frg_Away
IsambardPrince We are well beyond 57 Quantum with 2.53.17 already. Quantum was a marketing gag and not a new engine. Code level is mostly at middle of 59 with some parts like the build system much later.
-
njsg
should "scroll-behavior: smooth" still have an effect with the smooth scrolling preference disabled?
-
njsg
it's not affecting scrolling with the mouse or scroll bars, but if I click on a link to the same page, it affects the scrolling to the target
-
WG9s
i would think it should not but then perhaps the pref should be removed and it should all be css controlled
-
WG9s
pick one and stick to it otherwise is just confusing to the users
-
WG9s
either controlled via css or via pref but if there is a pref that should probably mean the css is ignored
-
WG9s
so if smooth scrolling is turned off by prefs then smooth scrolling enabled via css should be ignored
-
njsg
the CSS should mean the page designer wants to control whether there is smooth scrolling, the SeaMonkey setting is useful as a way to enable/disable it overall. Now unless there is a "Let page specify smooth scrolling behaviour" third choice, yes, it sounds like one should just override the other
-
WG9s
exactly
-
frg_Away
-
njsg
I guess the best solution here would be for CSS not to have smooth scrolling...
-
njsg
frg_Away: at least disabling the property in about:config fixes the scrolling
-
njsg
the property from that bug, I mena
-
WG9s
of course this is related to should we still support 32-bit and low ram configs sith old graphics cards people turn off smooth scrolling if 32-bit or even if 64-bit low ram and also if old graphics cards that canot to this all on their own
-
WG9s
everyone likes smooth scrolling unless they have hardware for which it makes the browser unusable
-
njsg
I've yet to find a graphics card configuration where smooth scrolling an animations aren't just annoying for me
-
njsg
I personally find it more confusing than just getting to the destination, too
-
njsg
and there's also the accessibility part of this
-
WG9s
is this a facebook issue where facebook decides to sroll the newsfeed such that the thing you were viewing disapears? i don;t htis has anything to be with smooth scrolling this is about the facebook UI just sucks.
-
njsg
WG9s: no, this is clicking a link to an anchor in the same page
-
njsg
-
njsg
-
WG9s
seems like the matrix brige issues continue
-
njsg
I think it's being shut down
-
njsg
deadline for that was 1400 UTC
-
WG9s
no deadline i thought was aug 14
-
WG9s
or was it aug 11 i don;t remebwr but i think was ona date that is still in the future
-
njsg
"[Global Notice] The Matrix bridge is experiencing continued stability and privacy issues; we have requested it be shut down until they are resolved. Matrix have agreed to shut down the bridge no later than 1400UTC on Saturday. Feel free to ask further questions in #libera-matrix"
-
njsg
Announcement/notice was around 0000UTC... last night? I'm not sure I'm reading the backlog correctly
-
WG9s
yes seems things got worse with less cooperation form the matrix side (i am sure matrix is posting is on the irc side)
-
WG9s
so the breakage happened earlier thatn previously advertised becasue the matrix side outright refused to fix any of the issues on their end
-
WG9s
like i waid were i on matrix i suspect i would get a different story about what happened
-
WG9s
there was a dealine but eveidently matrix made it clear they were not going to change anything before the deadline so cutoff became today
-
frg_Away
I won't miss them
-
tomman
-
tomman
just what we needed, ActiveX Neo
-
frg_Away
tomman It is all perfectly safe. Trust me. Nothing can go wrong. And if done in Rust 200% safe. No lets make it 300%!
-
WG9s
the matrix bridge deadline which they evidently expressed zero interest in meeting was Aug 11 so that is why was unceremoniously killed today.
-
WG9s
they had previously agreeed ot fix the issues by aug 11
-
WG9s
was a 2 week extension on the date they had previously agreed to
-
WG9s
I have zero idea what the original vulnerability might be but seems the matrix end in being uncooperative in trying to fix whatever it might be
-
tomman
Who operates the bridge, Libera or Matrix/Element?
-
WG9s
i have no clue
-
WG9s
i am sure were i on matrix i would get a different story on the issue saying it is the libera chat people who are being uncooperative.
-
WG9s
i think the issue is the bridge is supposed to be a cooperatve things where the two sides are not cooperating.
-
WG9s
all was well but then something went wrong ant the two sides making the bridge were took adversarial positions.
-
CaptainTobin
here guys
-
CaptainTobin
-
CaptainTobin
don't expect anything don't ask for anything don't question
-
CaptainTobin
obey like a good dalek.. WELL IF I WAS A GOOD DALEK WHY AM I NOT VICTORIOUS
-
CaptainTobin
realllllllly gives you a sense of "well you should have known better than to come back HERE and rely on shit webtech to boot"
-
CaptainTobin
doesn't it?
-
CaptainTobin
the bridge is operated by element
-
CaptainTobin
libera only agreed orginally to a "couple of channels" a point they have reiterated
-
CaptainTobin
WG9s:
-
CaptainTobin
i agree that the likelyhood of service restroration in any form is low
-
CaptainTobin
libera doesn't give a shit they have the balls of most major open source projects they proved that when they pulled a reverse coup on freenode
-
CaptainTobin
i assume you guys would gtfo if it became nessisary
-
CaptainTobin
i would hope
-
CaptainTobin
since irc is the canonical location for activity for seamonkey you just went from hundreds to 38
-
CaptainTobin
granted it is likely better since someone keeps allowing me to speak but still
-
CaptainTobin
lol
-
CaptainTobin
basically like it or not I have made my self as much apart of seamonkey history as anyone else just by being here so that is kinda neat tho.. so not ALL bad just mostly
-
CaptainTobin
...
-
CaptainTobin
WG9s: what happened was I started relying on it for BinOC and it fell down.
-
CaptainTobin
now there may be no actual casual link
-
CaptainTobin
but it DID occure that way
-
frg_Away
CaptainTobin well IanN is probably the one using it most. I have seldom seen controbution from other matrix users. So I can live with 38 who care a bit more about the product. As for freenode the new owner was just an Elon copy then. I don't think everything was as clear as water there on both sides but overall bon voyage and don't look back.
-
tomman
tested the search providers issue on a clean profile on a spare 2.53.17 setup: all providers stick fine after a couple restarts
-
tomman
in the meanwhile Yahoo Argentina _really_ insists that nope, I do not need English Wikipedia, but my other additions are OK
-
tomman
I even tried adding Wikipedia EN while leaving Yahoo AR in place - after a restart Wikipedia EN was.... gone
-
frg_Away
tomman maybe start in safe mode and change it there. Any chance you can use a debugger to see if you crash or assert during shutdown? If you have a clean repoducible case in a new profile I can check.
-
njsg
tomman: so that yahoo argentina replacement only happens on the existing profile?
-
tomman
On this machine I only have one profile
-
tomman
might as well test here with a separate one then
-
njsg
on the other setup you couldn't reproduce it at all?
-
tomman
nope
-
tomman
tried restarting the browser several times, and the search providers stuck as expected