Recommended Posts

I have never tried Palemoon or Waterfox, but I have heard good things. Isn't the disadvantage to using them that they aren't updated as much as Firefox? While Firefox is now officially on version 18, they are still behind, aren't they? Do you get the newest features such as tab animations with them? Are they faster in terms of overall browser responsiveness and scrolling? 18 has been the best for me, but some sites still feel a little jerky at times. Thanks for the link for 19 beta!

I have never tried Palemoon or Waterfox, but I have heard good things. Isn't the disadvantage to using them that they aren't updated as much as Firefox? While Firefox is now officially on version 18, they are still behind, aren't they? Do you get the newest features such as tab animations with them? Are they faster in terms of overall browser responsiveness and scrolling? 18 has been the best for me, but some sites still feel a little jerky at times. Thanks for the link for 19 beta!

Yes, they are much more optimized. Palemoon is updated pretty often > http://www.softpedia.com/progChangelog/Pale-Moon-Changelog-141741.html , about every month there is an update :). Tab animations? You mean like colored tabs? Yeah I think Palemoon is really responsive.

waterfox is Dead

I know :/.. I started using it about 1.5 month ago cause I got tipped by another forum member about it's awsomeness for being a 64-bit browser only :).

Yes, they are much more optimized. Palemoon is updated pretty often > http://www.softpedia...log-141741.html , about every month there is an update :). Tab animations? You mean like colored tabs? Yeah I think Palemoon is really responsive.

I know :/.. I started using it about 1.5 month ago cause I got tipped by another forum member about it's awsomeness for being a 64-bit browser only :).

No, I mean the somewhat smooth animation you get when re-arranging tabs. It started since version 17 and is in 18 as well. Is that in Palemoon and Waterfox?

Anyone having a lot of crashes after updating to firefox 18.0 ?

I can use my browser for like 5 -20 min and then it crashes :/ it almost never crashed in latest firefox 17.

Think i have had about 30 crashes today -.- thinking about moving to chrome -.-

Anyone know how to downgrade with every add on, bookmarker, usertyles, greasemonkey scripts and settings/layout ?

Anyone having a lot of crashes after updating to firefox 18.0 ?

I can use my browser for like 5 -20 min and then it crashes :/ it almost never crashed in latest firefox 17.

Think i have had about 30 crashes today -.- thinking about moving to chrome -.-

Anyone know how to downgrade with every add on, bookmarker, usertyles, greasemonkey scripts and settings/layout ?

No crashes here, try doing a complete fresh install and update your video drivers and see if that helps.

No, I mean the somewhat smooth animation you get when re-arranging tabs. It started since version 17 and is in 18 as well. Is that in Palemoon and Waterfox?

Hm I don't know, but if not there should be an advanced setting wich users can go in an change settings that developers don't have as default.. Othervice it would be as an add on.

Yes, Aurora does not update automatically for a few days after the Nightly merge, so the code can stabilise.

Why would you follow a specific version through the cycle? That seems somewhat pointless.

All you would do is not get any new features for four months, and potentially lose features as they're backed out for not being stable enough. What benefit is there? (And you end up with the problem that your browser wants to update, but you are avoiding it ... sort of).

Yes it is so I am staying with 21.

Nope, I ran into the same problem. After ff18, everything just went to hell.

You can reinstall FF17.0.1 over the current one and it'll keep all your settings.

I just reinstalled my nvidia driver and i havent had a crash since, and the new firefox is faster than v17 :)

Some news:

HTML5 Scoped Style attribute support landed, also HTML5 <time> tag basic support landed but behind experiment forms preference entry. So this is some good progress in this department.

Now from Inbound, some interesting bug which I think matters to discuss, like I always I share.

API to mark depreciated api as a result of refactoring of code and conversion to aysnc API: https://bugzilla.mozilla.org/show_bug.cgi?id=812859

CSS3 Animation related fix: https://bugzilla.mozilla.org/show_bug.cgi?id=827717 , https://bugzilla.mozilla.org/show_bug.cgi?id=827698

Externally opened URLs may open in new private window: https://bugzilla.mozilla.org/show_bug.cgi?id=829180

64-bit offset in Audio/Video (nothing to do with FF 64-bit progress so relax): https://bugzilla.mozilla.org/show_bug.cgi?id=829223

Regression fix on Mac OS X: https://bugzilla.mozilla.org/show_bug.cgi?id=821329

GC (Generational GC preparation bug fixes): https://bugzilla.mozilla.org/show_bug.cgi?id=829372 , https://bugzilla.mozilla.org/show_bug.cgi?id=828607

Adding ability to run JS tests in parallel to build Firefox faster: https://bugzilla.mozilla.org/show_bug.cgi?id=827960

Ion Monkey regressing some sites (This fix also be included in FF 18.0.1): https://bugzilla.mozilla.org/show_bug.cgi?id=818023

Brian Hackett work on dense array related small contribution - JS Engine: https://bugzilla.mozilla.org/show_bug.cgi?id=827490

Download Panel - Library downloads view does not show end time of downloading: https://bugzilla.mozilla.org/show_bug.cgi?id=828247

Ion Monkey small failure fix in one benchmark: https://bugzilla.mozilla.org/show_bug.cgi?id=829277

[MemShrink] GC to DOM Workers: https://bugzilla.mozilla.org/show_bug.cgi?id=828887

XMLHttp Request Bug in DOM: https://bugzilla.mozilla.org/show_bug.cgi?id=608735

WebIDL: https://bugzilla.mozilla.org/show_bug.cgi?id=828532

Some Retina Display high dpi images: https://bugzilla.mozilla.org/show_bug.cgi?id=829258 , https://bugzilla.mozilla.org/show_bug.cgi?id=826999

In pursuit of making sites can't look into installed plugins, some progress work landed: https://bugzilla.mozilla.org/show_bug.cgi?id=757726

Keyboard navigation fail in Library Download View: https://bugzilla.mozilla.org/show_bug.cgi?id=828895

Networking: DNS related: https://bugzilla.mozilla.org/show_bug.cgi?id=826455

OS.File API related enhancement: https://bugzilla.mozilla.org/show_bug.cgi?id=802534

Social Panel bug under Mac OS X: https://bugzilla.mozilla.org/show_bug.cgi?id=828120

The <time> tag is different to the "time" input type, <time> is basically a span and has been supported for a while.

It seems Bug 777283 (The implementation of the input type) is only the support code, there doesn't appear to be a UI yet.

The <time> tag is different to the "time" input type, <time> is basically a span and has been supported for a while.

It seems Bug 777283 (The implementation of the input type) is only the support code, there doesn't appear to be a UI yet.

Sorry mistook, thanks for correction yes, because it does not have UI yet that's why it is behind preference.

I like the idea of hiding experimental properties behind preferences, it lets them stop using prefixes (Since that's gone so well thanks to WebKit browsers), and it means that you have to explicitly enable them if you want to test them (Which reduces reliance on non-standard properties, which is something else that'd be nice for WebKit to have)

Of course the downside is that it gets less testing, but that's an acceptable tradeoff to avoid polluting the web.

I like the idea of hiding experimental properties behind preferences, it lets them stop using prefixes (Since that's gone so well thanks to WebKit browsers), and it means that you have to explicitly enable them if you want to test them (Which reduces reliance on non-standard properties, which is something else that'd be nice for WebKit to have)

Of course the downside is that it gets less testing, but that's an acceptable tradeoff to avoid polluting the web.

Webkit also hide sometime properties behind build system flags or sometime in about:flags. Although I personally like Firefox approach more better and you point is also valid, proper functionality is better than half baked experience.

About gfx drivers and issues with them: don't be too quick to jump on specifically Mozilla or Nvidia/AMD or Windows as the cause - it's a very complex area.

Yes it is so I am staying with 21.

I don't understand how that was a response to my question? I'm not going to make you change, but I still have no idea why would stick to a specific version rather than channel.

About gfx drivers and issues with them: don't be too quick to jump on specifically Mozilla or Nvidia/AMD or Windows as the cause - it's a very complex area.

I don't understand how that was a response to my question? I'm not going to make you change, but I still have no idea why would stick to a specific version rather than channel.

I said yes, meaning that I agreed with what you posted and then I went back to using the Nightly builds. As you stated it makes no sense to follow say Fx 20 thru all of the stages-(Nightly-Aurora-Beta-Final)

Webkit also hide sometime properties behind build system flags or sometime in about:flags. Although I personally like Firefox approach more better and you point is also valid, proper functionality is better than half baked experience.

I think that's more Chrome than normal WebKit, but it is a step in the right direction. The main problem is that when properties aren't hidden, they get put on this "perpetually supported for compatibility" list, so they're never actually removed then. On the surface it sounds great (older pages don't break), but the flipside is that for the best compatibility with multiple versions you need to use the non-standard properties (Since the old behavior is kept maintained), and that starts leading to ingrained bad behavior (For the longest time WebKit had a bug on OS X that let you use PostScript names for fonts rather than their standard names, to this day I'm still seeing sites that rely on that bug, breaking in pretty much everything, etc.)

I think that's more Chrome than normal WebKit, but it is a step in the right direction. The main problem is that when properties aren't hidden, they get put on this "perpetually supported for compatibility" list, so they're never actually removed then. On the surface it sounds great (older pages don't break), but the flipside is that for the best compatibility with multiple versions you need to use the non-standard properties (Since the old behavior is kept maintained), and that starts leading to ingrained bad behavior (For the longest time WebKit had a bug on OS X that let you use PostScript names for fonts rather than their standard names, to this day I'm still seeing sites that rely on that bug, breaking in pretty much everything, etc.)

Yes, when browser companies ship half baked vendor prefix enabled support and mention about it, they are maintained and carry forward by developers for too long and they then don't change even when they go with original spec implementation which as result broke sites badly.

So putting experimental properties behind preference is great thing IMO. So no user mess up with them unless they become ready for prime time.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Posts

    • Go on, I'll bite. How does windows (nice comment on an 'article' which doesn't actually involve it ) lock users out of their data then? Been using it since 3.1 back in 92 and not once have I been locked out of my data? Perhaps you mean Bitlocker? In which case the average user (who doesn't mess about) will have been forced to use a MSA, and in which case the recovery key would have been saved to said account..... If the user did happen to bodge around and not use an MSA then Bitlocker wouldn't have become live (as it cannot without a safe place to store the key) I want to point out Bitlocker and MSA are not connected and you can of course force it on without a safe place to store the key, but you do that with your eyes open. So your standard consumer who knows no better sets up an MSA, gets bitlocker and a recovery key stored off box, with a route to reset their password. All of this notwithstanding the fact, if your data is important, you back it up, no ifs, no buts, no-ones responsibility other than your own. Important data lives in at least two locations, one of which is offline and recovery is tested, otherwise that data wasn't really that important. Disks, fail, laptops get lost, phones end up down the toilet, tablets get stolen, if your only copy of data is on a single device you're doing it wrong.
    • Clearly that feature isn't for us. It's for the ad spam marketers so they can more directly target us about going to places we might want to go again...but without understanding context clues. Like for the flight someone took for a friend's funeral. We want to be reminded of that every time we open an app, a browser, or email, right? Right, Siri?
    • Is your Apple Watch supported? Check the watchOS 27 compatibility list by Aditya Tiwari Apple kicked off WWDC 2026 with a ton of announcements, mostly centered around Apple Intelligence improvements, the Siri AI, and Liquid Glass updates. However, there is a lot of other stuff that couldn't catch the limelight. Let's talk about watchOS 27 and which models are supported by the newest operating system. According to the Cupertino giant, watchOS 27 will be supported on the following Apple Watch models when it arrives later this year: Apple Watch Ultra 3 Apple Watch Series 11 Apple Watch SE 3 Apple Watch Series 10 Apple Watch Ultra 2 It's a stark contrast with last year's watchOS 26 update, which had almost a dozen Apple Watch models in its list of supported devices. Apple supported models all the way back to Apple Watch Series 6. That said, if you own one of the five models, you'll need an iPhone 11 (or later) with iOS 27 to install the latest update. Yes, Apple has shown some extra love to the iPhone 11, and it old horse supports the iOS 27 update. watchOS 27 beta 1 is now available for developers and interested power users through the Apple Developer Program. So, if you're among those who like to play with fire, you can download it to your supported Apple Watch. Otherwise, the public beta for watchOS 27 will be available next month. The freshly baked Apple Watch update comes with Siri AI - an advanced, fully conversational version of Siri powered by Apple Intelligence due for later this year. A new dynamic app grid features icons for five Siri-suggested apps. You can use a new tap gesture to open a widget in the Smart Stack, and a new Find My app finally clears the mess of Find Devices, Find Items, and Find People on Apple Watch. Workout Buddy can run without an iPhone nearby and offers new insights based on data, including your progress for pace, distance, and workout duration. Apple improved its motion tracking algorithms to measure the distance of indoor treadmill runs and walks more precisely. Speaking of other changes, the music playback on watchOS 27 starts faster and you can create custom passes for any membership or card that uses a QR code or barcode, then easily access them in the Wallet app or pin in the Smart Stack.
    • "and pull old flight details from your email during back-and-forth conversations" The Siri I've become to know and trust. I've always wanted to pull info on old flights. /s
    • Apple unveils Siri AI, a "reimagined" version of SIri by David Uzondu Image via Apple Today, at the opening keynote of Apple's annual World Wide Developers Conference (WWDC), the company announced Siri AI, a "reimagined version" of its voice assistant that runs on Apple Intelligence. Siri AI helps you do things like draft messages, edit photos, and pull old flight details from your email during back-and-forth conversations. You can access Siri AI through several methods, depending on the device. While "Hey Siri" remains active, iPhone users can also press the side button, swipe down from the Dynamic Island, or use a system-wide context menu on Mac to analyze on-screen text. Image via Apple If you ever need to go back and check previous interactions, you can open the dedicated Siri app to view your entire conversation history. This application privately syncs your data using iCloud, leveraging local Foundational Models alongside Apple's secure Private Cloud Compute servers to keep user data inaccessible to outsiders. On the iPhone, Apple built the assistant into the Camera app, bringing Visual Intelligence to help you split bills or count calories. This feature also expands to the iPad and Mac, letting users use screenshots or shortcuts to analyze images, while Apple Vision Pro users can ask questions about objects in their physical room. Other things to know about Siri AI include systemwide dictation that automatically handles punctuation and formatting, customizable voice speeds, and a spatial 3D interface built for Apple Vision Pro. Apple also added Smart Stack suggestions on the Apple Watch to help you continue recent conversations directly from your wrist. The road to Siri AI was quite bumpy for Apple, which initially promised these capabilities at WWDC 2024 when the Cupertino tech giant debuted Apple Intelligence. Apple later turned to Google, signing a $1 billion annual deal to use Gemini models instead of relying solely on its own in-house systems. However, this deal came only after consumers sued Apple because features Apple promised "did not exist at the time, do not exist now, and will not exist for two or more years." Siri AI is available for developer testing on iOS 27, iPadOS 27, macOS 27, and visionOS 27.
  • Recent Achievements

    • Very Popular
      Captain_Eric earned a badge
      Very Popular
    • One Month Later
      amusc earned a badge
      One Month Later
    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
  • Popular Contributors

    1. 1
      +primortal
      513
    2. 2
      PsYcHoKiLLa
      236
    3. 3
      ATLien_0
      85
    4. 4
      +Edouard
      77
    5. 5
      Steven P.
      76
  • Tell a friend

    Love Neowin? Tell a friend!