r3dfox, a modern Firefox based web browser for Windows Vista, 7, and 8!

[K4sum1]

So I just shouldn't work on r3dfox is what you're saying? I like adhd hop between projects and r3dfox is taking a backseat currently, I don't even know if I want to release a v152 yet. I don't feel like diagnosing this when I didn't touch the code myself, I would have to trace and debug and it's a lot of work and effort for something I myself don't use. I do wish the feature worked, but I just don't feel like diving into it.

This also does not affect ESR 140.

[user57]

hmm when you either stuck, dont want to make more of releases, coming to an end, versions dont go high quickly

then it might be time for the same thing as in the supermium 

then it would be time for a user agent changer, build in 

[NotHereToPlayGames]

6 hours ago, Jody Thornton said:

e3k-blah (I friggin love that)

I'm seriously wondering what the significance is, ie, the "viral" aspect is, of that number THREE.

e3k-blah...  r3dfox...  probably just overthinking it, but that 3 just feels like some "viral meme" that I'm just not "hip enough" to know.

[NotHereToPlayGames]

4 hours ago, user57 said:

then it would be time for a user agent changer, build in 

I disagree.  For one, the user agent is ANCIENT TECHNOLOGY that is DYING, DYING, DYING.

And for two, we should never lump Firefox forks (r3dfox, this thread) and Chromium forks (Supermium) into that sort of direct comparison.

No offense, but web sites that still do use the ANCIENT TECHNOLOGY of the DYING user agent isn't exactly (pro and con) up to par with the latest "googleims" and therefore stuck with Site A relying on a faked OLD user agent, Site B relying on a faked RECENT user agent, Site C relying on something totally in the middle, and therefore those OLD SCHOOL web sites can never use a ONE-FOR-ALL user agent, you will always have to rely on the "user agent override" settings in about:config.

[VistaLover]

6 hours ago, K4sum1 said:

I don't feel like diagnosing this when I didn't touch the code myself, I would have to trace and debug and it's a lot of work and effort for something I myself don't use. I do wish the feature worked, but I just don't feel like diving into it.

If it makes any difference, the "missing-titlebar-bug", 

https://github.com/Eclipse-Community/r3dfox/issues/177

https://github.com/e3kskoy7wqk/Firefox-for-windows-7/issues/147

, is caused by a change between v151.0a1-v4 (last GOOD build of the 151 branch) and v151.0.2 (first BAD build of the 151 branch); so, not that big of a "regression window" to dissect ...

[user57]

10 hours ago, NotHereToPlayGames said:

I disagree.  For one, the user agent is ANCIENT TECHNOLOGY that is DYING, DYING, DYING.

And for two, we should never lump Firefox forks (r3dfox, this thread) and Chromium forks (Supermium) into that sort of direct comparison.

No offense, but web sites that still do use the ANCIENT TECHNOLOGY of the DYING user agent isn't exactly (pro and con) up to par with the latest "googleims" and therefore stuck with Site A relying on a faked OLD user agent, Site B relying on a faked RECENT user agent, Site C relying on something totally in the middle, and therefore those OLD SCHOOL web sites can never use a ONE-FOR-ALL user agent, you will always have to rely on the "user agent override" settings in about:config.

fact is some of them are doing this, and they will do this in the future
why you just cant fix it ? what stands against that ?
you leave up an option you certainly can fix - so to say i also understand it
its a one time fix, its not like you have to bring out 150 versions of it

ancient or not they are doing this but that i already said

and the other thing 
both firefox and chrome have these - why we can not compare them in that matter ?

what they are trying is a version check - while they offer zero new functionality
a solution for this idiocy is to fix exactly that - a changeable version
then they no longer can point out that bullXrap

instead they have to rely on a new functionality - what they often dont do

its like with a d3d9 vs d3d10 question - there is barly any improvment either video or 3dmodels
and what they would do they would make a check for d3d10.2 and say - ha see now this dont work anymore
for what purpose ?

[NotHereToPlayGames]

1 hour ago, user57 said:

why you just cant fix it ?

Well, two things here.

1) There really is zero reason for r3d to fix what HE DID NOT BREAK.

2) We-the-consumer can just slip back to a previous version - IT AIN'T GONNA HURT YOU ONE D@MN BIT TO USE A PREVIOUS VERSION.

 

This is where the Browser Universe is just a bunch of whining babies, it really is the biggest STUPIDITY on the planet that browsers are updated so d@mn fast and no matter how fast it is, there are always folks that want it FASTER.

FASTER is WHY we have issues like this.  Because the ecosystem is all about pushing updates out fast, fast, fast.  INSTEAD OF TRULY TESTING THOSE UPDATES BEFORE SENDING THEM OUT INTO THE UNIVERSE.

And we end up with an ecosystem that is "happy" because they get FAST updates instead of GOOD updates.

Send out VULNERABILITIES all day long, nobody really cares, "because they fix them fast".

No, what we have is that they CREATED those vulnerabilities and sent them out to a population DEMANDING faster update cycles.

PUBLIC GOT WHAT THEY WANTED.

[user57]

we talk a little away from each others, the "fix it" part was for notheretoplaygames not for K4sum1

 

and we have like 100 % the same meaning:

"2) We-the-consumer can just slip back to a previous version - IT AIN'T GONNA HURT YOU ONE D@MN BIT TO USE A PREVIOUS VERSION."

 

i totally agree on that one, but what notheretoplaygames also says is that he has to much of upgrades he says always something like "that upgrades go a little to fast"

but here is where i tryed to point out you can fix this version trick - i dont have to repeat what i wrote about that, its a version trick in short again

also you only missing the part with version 8 - thats the last one from the "common trick list" - there are certainly more - but having these would be ok for now

and it does indeed work against that "fast upgrade problem"

 

the other part regarding the user agent - if r3dfox has a problem with the new versions - yes the user agent is a solution that work against that - it might not fix it totally - but it would be a step into the right direction

that same thing also goes for supermium - what is even the problem to searching for the value that is being added to not_a_brand  with "version 8" ? thats the only thing you missing, its only 1 thing