Browsers
-
A Former User last edited by
Not going to start another "Firefox" topic, I'll just ask you a question.
Well, I updated my 3.6 and 4.0 to 8.0 and 12 respectively.
Everything went, well, better.
No more black screens on updating plug-ins... Till now...I got my
ShockWave
red, hit the button, and got this. Tried hitting the cross,Esc
- no avail, at all. "Manage acc" - don't remember exactly, some BS; "sign out" led me to a page to log in (:WTF:).
Do you think my Foxes can't render the page? Or is it something weird with the Adobe site? Both?
If former - can I try updating the plugin via another browser (I saved the link)? Only I do not want any trouble nor mess caused to that other browser, please!Here's the printscreen: .
Yes, the picture's the same with both Foxes. -
A Former User last edited by
Maybe I should, Sidney, but there's this thing: for my Russian installation (3.6) I got a 8.0 I'd already had downloaded, while for my British one (4.0) I hit the
update
button in the browser - presuming "update to the latest version", right? And it updated. I didn't know it was only 12.0 - till I checked it.
So, that's it.
What about my question? -
A Former User last edited by
Can you pass me the link you tried to open? please
No problem, https://helpx.adobe.com/security/products/flash-player/apsb15-01.html
(must be it). -
A Former User last edited by
No more black screens on updating plug-ins... Till now...
I got my ShockWave red,
...O'k, I'll tell you something.
Yesterday I was forced to reboot the workstation. Upon the previous reboot (after "lights on") I had another Adobe Reader window/notification to update - I hit "later". Now I had it and didn't - installed.
Guess what? 8.0 started - no more "outdated plugin" notifications.
It's only happened once since "I agreed" this time - one time started the Fox and no shit - so it's not certain, but still...However, that weirdo about the Adobe site disallowing me from using it, requiring some outrageous logging in stays as a question. If anybody else encountered that, or this repeats, it might deserve a topic of its own - about Adobe BS.
-
A Former User last edited by
Google Chrome started sucking recently - bugs on Facebook, other issues.
I kinda like its interface and all, but, having recently updated my Mozilla herd with some recent version(s), I've found I could use my Firefox now for most purposes: smooth loading, Facebook doesn't seem to glitch there, etc. -
A Former User last edited by
Google Chrome started sucking recently - bugs on Facebook, other issues.
... I've found I could use my Firefox now for most purposes: smooth loading, Facebook doesn't seem to glitch there, etc.My antimalware software might have corrupted my Chrome by wiping out some files - not many. It works though.
The other thing is, I can't abandon Chrome altogether because its having certain features Firefox doesn't: on Facebook, I can post the clipboard image directly to the chat or even post update with Chrome but not with my Firefox ;_; -
A Former User last edited by
How many browser engines are there?
Having a shortage of up-to-date browsers here, I'm willing to try something other than one and the same Chromium.
I mean my Firefox might still be on Gecko, and my Opera 11 is HOT :love: but...
Where one spits, there's Chromium now: Vivaldi, Schmivaldi, whatever.
Well, I don't mean IE, of course: having this 11 here, I might not even know how to use itYes, the old Opera's one is the best forever.
Having a task like to play games and watch movies, my 11 is THE ONLY one to NOT HAVE ANY stuttering. EVER. :happy: -
blackbird71 last edited by
How many browser engines are there? ...
Roughly speaking, there's about 18 engines, of which only about 13 will run directly on a Windows desktop/laptop. Of those, around 8 engines are used in the more commonly recognizable browser names. Moreover, many of those 8 engines are simply forks or offspring of other engine designs, bearing many of the same characteristics and limitations as their parents.
In reality, there are only 5 primary engine lines currently being used for Windows browsers: all the variants within the KHTML/Webkit/Chromium/Blink lineage, Gecko, Trident, Presto, and EdgeHTML. As you've observed, the largest array of browsers currently exists based on chromium/Blink engines, largely because that engine is open-source and maintained by the chromium consortium, thus sparing the browser makers from having to maintain it themselves.
-
A Former User last edited by
Thank you, Leo!
And Presto is owned by Opera and that's it, right?
Which meansread the first lines of that post of mine
- boooring! -
A Former User last edited by
Yep, Presto is/was the engine of old Opera.
It still is - many people do still use Old Good Opera. For now...
-
A Former User last edited by
In reality, there are only 5 primary engine lines currently being used for Windows browsers: all the variants within the KHTML/Webkit/Chromium/Blink lineage, Gecko, Trident, Presto, and EdgeHTML.
Firefox are going to abandon Gecko, aren't they?
So - what are we're gonna be left with then?
- Chromium.
- Chromium.
- Chromium.
- Chromium.
- Windows' Edge.
:rip:
-
threatdown last edited by
In reality, there are only 5 primary engine lines currently being used for Windows browsers: all the variants within the KHTML/Webkit/Chromium/Blink lineage, Gecko, Trident, Presto, and EdgeHTML.
Firefox are going to abandon Gecko, aren't they?
So - what are we're gonna be left with then?- Chromium.
- Chromium.
- Chromium.
- Chromium.
- Windows' Edge.
Firefox is not abandoning Gecko, and definitely aren't adopting chromium. They have an experimental new engine called Servo, but it's mainly for research purposes and they plan to integrate parts of it into gecko over time.