firefox is not unix, it is something horrible

I dunno. I went -current through 13, 14 and 15 without problems I would notice. I don't see a more reckless approach, unless somebody screwed up release-near merging.
 
smithi don't over-think it :)

Ok. Glad you're still smiling.

No recollection of that.

Too many rabbit holes ago ...


At least it means what I thought it meant, but I accept you didn't mean it that way.

With rules and guidelines as (collectively) a good thing, I see nothing negative about drawing attention to the positive.

Americans talk of "nailing jelly to the wall" which seems apt, re this now seriously off-topic aside. I'm more than done.
 
After a forced upgrade of firefox, the cursor does not change anymore when it is over a link.

Do some knows the problem and solution?

It is terrible that after each upgrade one must waste time deactivating the new and old "features",
something that needs always different procedures.

I am still waiting that a viable alternative to this horrible bloat appears.

UPDATE:
Go to "about:config" and change "widget.gtk.legacy-cursors.enabled" to true. Then you get the used behaviour.
The new the non-legacy "feature" is, as always, no improvement, but the contrary.
The upgrade is in reality a downgrade.
 
From what version to what version?
I just upgraded from Firefox 138 to Firefox 150 incrementally in two days, compiling it from source, there have been no issues. (Incrementally precisely because I wanted to make sure there were no issues).
 
The new the non-legacy "feature" is, as always, no improvement, but the contrary.
Yeah, basically they were scared of the year 1984 for some reason and wanted to break all software still relying on code from that time.

https://bugzilla.mozilla.org/show_bug.cgi?id=1876366#c15

These guys must really hate computers. Though this breakage happened almost 2 years ago; why is it just propagating into FreeBSD now? Did we used to host patches to fix this breakage?
 
"Recently, Gnome decided that it doesn't like the old cursor names and removed all of the old standard cursors from their cursor theme!" - this sounds stupid. Why? To save disk space or lower number of files?
 
The only browser I was ever satisfied with were Opera in 2000s.

Think about it it should've been a fat piece of turd, IE5/6 and Netscape were no slouch when it comes to consuming resources, now there is browser out there with fully customizable UI, tabs, download manager, IRC, email (and torrent later on), and it is lighter and faster than them.

That kind of thing is not going to return, the web of those days is gone, everything is 1000x more heavy now.
 
The only browser I was ever satisfied with were Opera in 2000s.
I also.

I have used MOSAIC and its children from the beginning in 1993 so changeling that after 33 years ..........
is probably not happening.
Mosaic was the first graphic browser I used, then someone, in irc if I remember correctly, recommended
me netscape, and with firefox I am till now using it, but not really voluntarily as at the beginning, I am fed
up of this repugnant bloat.
 
Now I discovered another "feature".

When the mouse is over a tab, the cursor flickers, it oscillates between arrow and cross (like mouse on root).

No idea how to repair that. Wait till next release with new "features"?

UPDATE:

The problem disappears if I do not start firefox with:

env XDG_SESSION_TYPE=x11 XDG_SESSION_DESKTOP=twm firefox

But then context menus when clicking a link with right mouse key disappear when one releases right key.

A different solution is to use other window manager, for example fvwm.

This so repugnant buggy.
 
Opera looked incomplete. Netscape 3 was good, then IE5 and IE6. Browsers were acceptable when JavaScript was turned off by default and not necessary.
It would be an improvement today. What a piece of garbage Javascript is. It's kept up by the advertising empire. The primary goals are personal tracking and artificial obsoletion of computers.
 
I don't know, I have zero problems with Firefox now. But I am definitely never using X11, only Wayland...that's the first thing you should fix. If you don't use Wayland, you are asking for trouble.
 
But I am definitely never using X11, only Wayland...that's the first thing you should fix.
I will not "fix" that, I would either trash the programs that not work with X11.

For long time X11 was praised as something good, networked and better (as an idea) than local GUI of Windows.
And it is a better idea and a wonderful piece of software.

It lacks of good judgement to recommend to trash a good working program to satisfy a trash program like firefox.
 
I'm on 16.0-CURRENT now firefox-151.0.2,2 and the cursor changes on link hover with widget.gtk.legacy-cursors.enabled false
Good to know.

I use firefox-esr, because at some time it avoided problems that "new features" introduced in the normal version.

If they solve something, they spoil at the same time other things, as you see in my post above about XDG_SESSION_DESKTOP.

It is not software that develops toward perfection, bug fixes, security, but software that unnecessarily inflates, bring more bugs as they eliminate.

I really got upset by the recommendation to dismiss X11 for using firefox.

The question is, if there will ever be an alternative to firefox and chrome.
The trend is that at the end we all be compelled to use chrome (that seems to be better than firefox).
 
Do you agree?

If you find with google a pdf file, you cannot get the URL, because it downloads the file and presents a local URL to the downloaded file. In particular, you cannot do a bookmark to the original URL.

Copy with mouse key1 in the results of google and trying to paste with key 2 bring troubles.

It is highly configurable, one can configure a lot of stupidities, but it is from time to time unusable.

Well, a lot of strange things, in some way strange for a unix user with simple X11 with twm.
I don't quite understand... if I find a pdf with google, I can just right click on the link, copy link, and then download it separately. Or you can change the default action like this https://support.mozilla.org/en-US/questions/1433839
Maybe I'm misunderstanding you...
 
This is pure bullshit on Mozilla's part, the internal PDF.js should only be used if there is no MIME handler for PDF in the OS.
PDF.js is damn slow. Most of my PDF consumption is spec sheets, manuals and digitized documentation, and PDF.js is so slow to render pages of documents that are scanned to full-page graphics.
 
Back
Top