Firefox 28 Arrives With VP9 Video Decoding, HTML5 Volume Controls
An anonymous reader writes "Mozilla today officially launched Firefox 28 for Windows, Mac, Linux, and Android. Additions include VP9 video decoding, Web notifications on OS X, and volume controls for HTML5 video and audio. Firefox 28 has been released over on Firefox.com and all existing users should be able to upgrade to it automatically. The full release notes are available. As always, the Android version is trickling out slowly on Google Play (Android release notes)."
Mozilla also announced tools to bring the Unity game engine to WebGL and asm.js.
Installed the update and it didn't turn my laptop into a smoking crater on my desk; so far, so good..
Are YOU using the TOOL, or is the TOOL using YOU? Think about it!
...and all existing users should be able to upgrade to it automatically
Not for those of us running Gentoo linux.
We have come full circle. The rationale for 'puting x in the browser' is so that I wouldn't need x software for y platform...just a browser.
Nowadays browsers have so much functionality built-in they weigh a ton[in memory]. I don't want all that shit. Just show me the static content. Keep the spinning rims for the simpletons.
TLDR; I long for the days when all my browser could do display static content. All I ever wanted was standardized media formats[without DRM]
I've had a love / hate relationship with Firefox for many years - but for about the past 18 months it's been mostly stable.
I'm an extremely heavy browser, ranging from 20 to 150 tabs open at a time.
This latest build (27.0.1) has been utter shite for stability, so I sure hope that was a priority for them. It would be nice if a single tab crashed it would just take out that tab. If that means more processes or memory, so be it. Also please copy chrome ASAP with the little microphone representing the noisy tab.
No. Seriously?
I can see 20-40 tabs. But 150?
Chas - The one, the only.
THANK GOD!!!
Mozilla also announced tools to bring the Unity game engine to WebGL and asm.js.
I think I'll stick with the plugin. I've never had that crash on me. WebGL, on the other hand, crashes every time it is used. I can't even get through the conformance test with a FAIL, it crashes in multiple places and tests (and not the same one each run). And don't say it is my graphics card driver. IE makes it through just fine without crashing and FF used to not crash up until a few versions ago. Maybe they should fix whatever is wrong with the WebGL implementation before they start making people actually use it.
150.
Onehundredfifty.
What do you do with your day? I sure as hell hope you're getting paid to do that.
So what's the use for VP9, I just tried youtube and it still wants adobe flash...
If you currently have automatic updates on, this release of Firefox is the one where you probably want to turn them off.
There's got to be a point where open tabs are treated like temporary bookmarks. Trying to keep all of those tabs alive and ready to click on is a huge waste of resources.
09F91102 no, 455FE104 nope, F190A1E8 uh-uh, 7A5F8A09 that's not it, C87294CE no. Ah! 452F6E403CDF10714E41DFAA257D313F.
I know slashdotters are probably sick of seeing comments like this, but can we get some actual hardware acceleration on Linux already?
HTML5 is never going to be a viable replacement for flash while the renderer only draws in software via cairo.
It would be nice if a single tab crashed it would just take out that tab. If that means more processes or memory, so be it.
https://wiki.mozilla.org/Electrolysis
>If that means more processes or memory, so be it
NO. Please god no. At least think about how to improve on Chrome's really basic implementation of the idea. I don't want most of my RAM eaten up because some people can't use a decent Session Manager addon and wait 10 seconds for Firefox to restart. It's really not worth it if the best they can do is copy Chrome.
>please copy chrome ASAP with the little microphone representing the noisy tab.
They are trying to, but Flash makes that very difficult (perhaps even impossible) right now. When Google and Adobe got together and designed a Chrome-specific version of Flash using PPAPI, they were able to do this. Now Firefox is waiting for Adobe to give a shit about doing the same kind of thing for NPAPI for Firefox. No news yet, so Mozilla is working on replacing Flash with their own HTML5 version called Shumway.
I have had issues with this for quite some time... I try chrome every now and again, only to be disgusted with the lack of decent addons. heh
Also please copy chrome ASAP with the little microphone representing the noisy tab.
The problem seems to be with Flash. Chrome has native Flash rendering, Firefox still uses an Adobe plugin that has no interface for the browser to know if it's rendering audio. bugzilla discussion One more reason to get rid of Flash. Of course what Firefox could do right now is indicate the tab with the noisy HTML5 player.
You may want to read this: http://www.ghacks.net/2014/01/15/main-reason-chrome-tab-audio-indicators-firefox/
... until they've finally commited to a stable API regarding themes and extensions.
When I do upgrade I only find that NONE of my two (!) extensions work for weeks.
So f*** you, upgrade path.
I don't like the UI for chrome, some of the decisions Google have made are quite gross, they really are becoming Apple with their "our way or the highway" approach.
No question chrome is fast, won't deny that for a second - but I just prefer FF - I can customise it to my needs.
(Disable tabs on top, add "tabs menu" addon, use tab mix plus - with very specific open / close / foreground and background ruleset) - stuff like that.
Unless you're going to be submitting bug reports about the browser, or need bleeding-edge features (like VP9), you should just stay on the ESR branch:
https://www.mozilla.org/en-US/...
They make it hard to find, but I wouldn't use anything else... Those are the REAL stable releases, while their numbered releases are just betas.
With distros like CentOS/RHEL, the ESR version is in the yum repo, so you get a stable browser, updates are seamless, and you may not even notice the change when a new version gets installed.
Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
"bugzilla discussion" was supposed to link to the bugzilla discussion
Windows anymore? Didn't they just ditch Firefox for WIndows 8 metro mode a few days ago?
What happened to that new, easier method of Firefox Sync device pairing that was supposed to come out in Firefox 27?
The big issue with the current method is to add a new Firefox instance to the group, it pretty much requires you to have access to both your new device and an existing device simultaneously. Unless you save the authentication key file it's impossible to sync different Firefox installs on a dual/multi-boot computer or recover your saved passwords and bookmarks if a device is non-usable from damage or outright lost/stolen.
Good luck watching vector animated short films on Newgrounds or Albino Blacksheep or Dagobah without Flash. Rendering them to video (such as for YouTube) just makes them ten times bigger in my experience.
I was under the impression that Partner videos and videos with music in them didn't play in HTML5 mode.
Reductio ad absurdum is mutually exclusive of straw man not a subset.
Straw man is a common error when trying to build a reductio ad absurdum, if Wikipedia's article about the latter is to be believed. A lot of people end up reducing the wrong premise to an abomination or contradiction.
Exactly. You are working on researching one problem, but during that time are asked to look into 6 other issues.
Firefox is now (v 27.01) more unstable that it was before, and it has always been the most unstable program in common use.
Try the Pale Moon version of Firefox. Mozilla Foundation is run by a lawyer with no technical experience. The Pale Moon people seem more knowledgeable. Also, there is a 64-bit version of Pale Moon.
Firefox crash statistics:
https://crash-stats.mozilla.com/home/products/Firefox/versions/27.0
(Mozilla Foundation does not allow direct links from Slashdot.)
Many crashes do not start the Crash Reporter. Those statistics show only the crashes that do.
I use the Tree Style Tab plugin and usually have over a hundred tabs open as well. I'll keep the session open for days, too. It's easier than searching through your history to find that thing you saw a few days ago and the page is intact from when you loaded it last which is useful for dynamic content. Plus, everything is automatically hierarchically sorted, so it's easy to push and pop my browsing stack! Since I no longer own a a 4:3 monitor it's the perfect way to fill up the extra vertical space. It's an essential plugin for me now, up there with Noscript, Autopager, AdBlock+ and Ghostery.
Silicon & Charybdis McLuhan Kildall Papert Kay
Users of Windows 7 and Windows 8 should pay close attention to the Known Issues section of the Release Notes and and apply the workaround mentioned. The text rendering issue is quite severe.
This spam again? Don't you have anything better to do with your time than spew this nonsense every time Firefox is discussed? Does Pale Moon really need supporters like you, who have nothing to offer beyond unsubstantiated personal attacks, and an excess of bile toward the product that Pale Moon wouldn't even exist without? I don't know what scares me more, the fact that you've convinced yourself of this tripe or that you have supporters who blindly upvote you.
Right now I have Chrome running and tab outliner say 280 tabs.
This machine only have 8 GB of RAM but the idea was to get a new one with 32 GB and as such I have 16 GB of swap allocated on the HDD. Once it reach 5-6 GB the machine get awfully slow though so the 50% recommendation (Linux partitioning) is likely good.
I like Firefox but I use to kill -9 it to free up RAM and if necessary be able to go back later by using restore (eventually it will stop saving such info though, I have no idea why.)
The thing with Chrome (unstable) as I run now is that either some tab died or I killed it and I got that message about bla bla killed or ran out of memory. But you had a reloadbutton to get back!
Awesome. So now I run chrome and when the machine starts trashing I run top and sort after memory usage and kill a bunch of chrome threads and back my memory comes and I can keep on running.
Sure the tabs belonging to processes I killed will unload but it's no worse than just reloading them later.
So that would be my recommendation for you I guess :)
Killing -9 is not nice, I suggest you install a "restart firefox" extension like I used to have.
Or may be you do that too for getting the start up dialog that allows to clear the junk by unticking tabs.. Sucks that Firefox doesn't allow that without force killing it!, and there's no command line argument for that. There's probably an extension but it should be part of the default software. Or I need a "Crash" menu item.
Mozilla Foundation
Top 21 Excuses
for Not Fixing the
Firefox Memory and CPU Hogging bugs
These are actual excuses given at one time or another. They are not all the excuses, just the top 20.
1) Maybe this bug is fixed in the nightly build. [The same memory and CPU hogging bug has been reported many, many times over a period of TEN years.]
2) Yes, this bug exists, but other things are more important. [The bug eventually causes Firefox to take 100% of the power of one CPU, and makes Windows 7 unusable, even after Firefox is killed. The bug affects the heaviest users of Firefox, those who do a lot of research online.]
3) Yes, this bug exists, but it is not a common occurrence. [Numerous users have reported the bug. See the links.]
4) Works for me. [The bug is complicated to reproduce, so the developers did a simplified test, which didn't show the bug.]
5) No one has posted a TalkBack report. [If they had read the bug report, they would know that there is often no TalkBack report, because the bug crashes TalkBack, too, or a TalkBack report is not generated. TalkBack does not generate a report if Firefox is hogging the CPU. TalkBack cannot generate a report if the bug takes 100% of the CPU time.]
6) If you would just give us more information, we would fix this bug. [They didn't bother to reproduce the bug using the detailed information provided.]
7) This bug report is a composite of other bugs, so this bug report is invalid. [The other bugs aren't specified.]
8) You are using Firefox in a way that would crash any software. [But the same use does not crash any version of Chrome or Opera.]
9) I don't like the way you worded your bug report. [So, he didn't read it or think about it.]
10) You should run a debugger and find what causes this problem yourself. [Then when you have done most of the work, tell us what causes the problem, and we may fix it.]
11) Many bugs that are filed aren't important to 99.99% of the users.
12) If you are saying bad things about Mozilla and Firefox, you must be trolling. [They say this even though Firefox and Mozilla instability is beginning to be reported in media such as Information Week. See the links to magazine articles in this Slashdot comment: Firefox is the most unstable program in common use [slashdot.org].]
13) Your problem is probably caused by using extensions. [These are extensions advertised on the Firefox and Mozilla web site, and recommended.]
14) Your problem is probably caused by a corrupt profile. [The same bug has been reported many times over a period of five years. One of the reports discusses an extensive test in both Linux and Windows that used a completely clean installation of the operating systems, not just a clean profile. The CPU hogging bug and instability was just as severe.]
15) If you are technically knowledgeable, you can spend several hours (or days) trying to discover the problem: Standard diagnostic - Firefox [mozillazine.org]. [Firefox has "Standard Diagnostics". It has become accepted that some users will have severe problems. !!! ]
16) I won't actually read the (many) bug reports, but I will give you some complicated technical speculation. [This pretends to be helpful but, on investigation, is shown to have nothing to do with the bugs.]
17) It's understandable that Firefox developers become defensive when users report so many problems. [Translation: Firefox management is childlike, not adult.]
18) To spend smart developers' time going over reports of bugs generated by analysis tools would be a waste. [There have been 3 analysis tools recently used to find Firefox bugs, and many have been found: 1) A special tool designed by a Firefox developer. 2) Software by Coverity. 3) Klocwork's K
Ghostery collects and sells data from the plugin. Disconnect is equally functional, without the data collection.
Finally had enough. Come see us over at https://soylentnews.org/
That would be great. I've long been looking for a queue addon, but never been able to find one. I want to be able to queue links, but have them open and ready once I close the page I'm on - so a few pages should be loading already (these are often image-heavy pages).
Having anything after the first ten tabs as temporary bookmarks, pretending that they are tabs would do this, as long as when the first tab is closed, number 11 is automatically opened. That way, it should be done loading when I get to it.
Using multiple tabs (as I do now) also accomplishes this, but that does mean that I sometimes have hundreds of tabs open (I suspect that 100 is actually too low, but I don't know an easy way to count).
It's another FF release, and another chance for unpleasant discoveries of arbitrary, arrogant, and unwanted removals of essential features. E.g.,
920031 – Find text is not remembered between tabs (e.g. when Find Again)
https://bugzilla.mozilla.org/show_bug.cgi?id=920031
I love FF, but it seems to have Jumped the Shark somewhat, esp. in performance. On my Mac I end up restarting FF multiple times during the day.
At long last Firefox has full Flexbox support. Even Interent Explorer beat them to full support of this standard. If you regularly work with CSS + HTML, Flexbox is a god send and now we can finally start using it.
I mentioned that people who call themselves Christians but then commit acts of violence, for flimsy reasons and without provocation, are not in fact practicing Christianity. Some fool cried "hehe I guss there is No True Scotsman then huh?!" while patting himself on the back fiercely.
If someone wrongfully accuses you of creating a no true Scotsman (NTS) fallacy when discussing hypocrisy among self-proclaimed Christians, here's how I'd reply: "I've always defined 'Christian' as someone who follows the teachings of Jesus of Nazareth. Anyone who claims Christianity but materially fails to practice it is something else: a 'hypocrite'. In Jesus's time, there were hypocrites in the leadership of Pharisaic Judaism, and he tore them a new anus in a speech recorded at Matthew 23." Clearly defining the goalposts early on shifts the debate from "you moved the goalposts" to "is this person really practicing?".
This infantile fevered-ego shit is killing Slashdot much faster than a shitty Beta redesign ever could hope to do. It's just far less trendy to protest it.
The NTS fallacy usually has roots in disputes over definitions. Even Scientology recognizes the problems that misunderstood words cause. One can prevent the fallacy by agreeing upon definitions before proceeding, such as "Christian == one practicing Jesus's teachings". This is an anti-NTS step that any Slashdot user can help stop, unlike forced beta for which the only cure is leaving Slashdot in favor of Soylent News or Pipedot. Right now, one can turn off beta, but once Slashdot forces it, the only course of action will be to follow reasoning analogous to Jesus's advice to body integrity identity disorder sufferers in Mark 9:45: "If [Slashdot beta] causes you to stumble, cut it off."