Firefox 1.0RC2 Released


Recommended Posts

no need

just add that line in your user.js

user_pref("signed.applets.codebase_principal_support", true);

584862275[/snapback]

Or you can type about:config into the adress bar and scroll down until you get to it in there and then enable it by clicking the button.

Someone help me :)

I just installed Firefox RC2, all my bookmarks where ******, so i had to add them all again, but it didnt help.

When i first load up Firefox, my homepage doesnt load and none of my bookmarks are in the Boomark drop down menu. I have to go to manage bookmarks, click the link i want, and then they show up. Its all fine and dandy having them showing up, but now when i click them, nothing happens, no page loads what so ever.

I was surprised that all my extensions ported over with no problems. Lookin' good for the 9th!

584863126[/snapback]

thats because the version hasnt changed since RC1. RC1 and RC2 have been both labeled as 1.0 so that all extensions and themes will work throughout the testing phase and especially be working for the final.

Or you can type about:config into the adress bar and scroll down until you get to it in there and then enable it by clicking the button.

584862943[/snapback]

indeed

but this way you saying will write the option in your pref.js

I prefer having it in user.js which overwrite the pref.js

why? because in user.js, they stay sorted when you add comment to what you add/remove and when you backup your files during a major upgrade, you dont get lost

so even with 1.0 releases, you sill have to unninstall the previus built, before you install the new one?

Whats the best way to upgrade Firefox, to keep all your settings?..

Thanks.

584864013[/snapback]

i think you can install right over it, but i always backup my files and do a clean installation. it seems to be better for me.

I installed over my installation and everything went smoothly. In the about section it clearly says RC2, so that at least ported over. It looks good here, if people have problems installing over their installation, I'll start starting fresh, but for now it's working fine.

I don't think I will download the release candidate, especially with only a few days left until it is officially released.

584861552[/snapback]

They release these builds because they want people to test them. It is like Democracy compared to Micro$oft's tyranny, they want to make the best product and they listen to the people, rather than the marketing department. By using these builds and sending them feedback you help to make Mozilla a better product.

You don't have to do this though, I'm just saying there is method to their madness. :D

They release these builds because they want people to test them. It is like Democracy compared to Micro$oft's tyranny, they want to make the best product and they listen to the people, rather than the marketing department. By using these builds and sending them feedback you help to make Mozilla a better product.

584866073[/snapback]

Hold on a minute. Are you inferring that Microsoft doesn't allow people to beta test their products and only they don't listen to their customers? You, sir, need to get a clue of how things work.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I think the car analogy is more this: Left hand drive, basic commands on the left side of the infotainment screen. Right hand drive, basic commands on the right side of the infotainment screen. Granted, you're not swapping between the two often so it's doesn't really work. But it's to do with the proximity of you (your mouse, or the driver) to the controls.
    • I mean, the old one was broken and so stupidly complex for many users, so I don't see that as a feasible option. A context menu needs to be simple to use, and for me the Windows 11 style actually worked really well for me, and many others. I used to have to scroll the damn context menu just to get to "file properties" in Windows 10. That was not a good experience, and I'm sure you'd agree. What they're trying to do is make it the best of both worlds, as clearly you'd prefer the Win10 style. I'm curious how they're going to do this.
    • The "Show more options" has its place, as does the simpler context menu, but it should perhaps be a separate fly-out rather than relaunching the entire, old context menu. The old context menu was getting absurd in Windows 10. Often I'd have to make the context menu scroll just to get to "File properties" on my old laptop. Even without much installed, the amount of items was just too much. It's a context menu, not a "do all" menu. Making it configurable is fraught with challenges too, so I'm interested to see how Microsoft tackles this one.
    • I don't hate the new menus, I am not a fan of the lack of features and how they went live when they clearly are not complete. The menu itself presents much better than the previous - but what's lacking (IMO) is: 1) Any kind of automated manipulation such as: "this goes on the new menu because you use this feature more often on this filetype" "this is rarely used and will fall back to the old menu" 2) Any kind of user manipulation such as: "a UI to add/remove/order items to the new menu"
  • Recent Achievements

    • Week One Done
      I2D earned a badge
      Week One Done
    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
    • Very Popular
      s0nic69 earned a badge
      Very Popular
  • Popular Contributors

    1. 1
      +primortal
      484
    2. 2
      PsYcHoKiLLa
      262
    3. 3
      Skyfrog
      86
    4. 4
      FloatingFatMan
      64
    5. 5
      Michael Scrip
      63
  • Tell a friend

    Love Neowin? Tell a friend!