Recommended Posts

To clear this up:

8.How do I capitalize Firefox? How do I abbreviate it?

Only the first letter is capitalized (so it's Firefox, not FireFox.) The preferred abbreviation is "Fx" or "fx".

Source

But this is from the Firefox 1.5 release notes, early in the development of Firefox. Note that it says preferred. Regardless, it does not matter what the abbreviation for Firefox is.

Anyway, thanks for the heads up. I updated through the software update.

It has, it is and always will be "FF". Sorry.

Wrong. It has been "Fx" since the name was changed to Firefox, at least among the community here and in the Mozilla community. Before that it was "Px" and "Fb" when the names were Phoenix and Firebird, respectively. As far as "always will be," they've changed the name twice before so I wouldn't be so quick to claim that with such certainty.

You should be calling Firefox... Firefox. Your analogy reminds me of the people who actually use "LOL" as a word in spoken conversation.

Ah hell they added favicons and folder icons to the bookmark toolbar in OS X. I liked it without them. I wanted Chrome without them and now the icons are in FF too. :(

You should be able to use the same script we Windows users use in Stylish or in your userChrome.css to remove them.

Touch has worked well in FF for a while. unless something new that I didn't know about was just implemented. That is entirely possible. Chrome has about the worst support for touch out of all browsers.

Apparently I missed it, but multitouch features have been added. Nice demo they had. Digging FF4 beta 3. Looks great, quite speedy.

I got an email from Mozilla about a Test day that is occuring this Friday, the 13th. Looks like Tab Candy should be ready by the end of this week.

I'm not sure I believe that, or at the very least they'd have to have a much looser definition of ready than I do, because the build I tried from just a few days ago STILL had a black wherever there was supposed to be glass. However, if they manage to fix that and release it by Friday there will be much rejoicing.

Just call it "F" then since it's one word. Please stick to the topic of the Beta 3 release.

This thread is redundant, anyway. You might consider merging it with the Firefox 4.0 beta thread that's been ongoing for weeks @ https://www.neowin.net/forum/topic/896934-meet-firefox-40-beta-3/page__pid__593019490__st__1440entry593019490

Using any custom themes or such? The main issues with Aero Glass got fixed before Beta 1 branched.

Edit: I actually think there is some issue with Direct3D Layers and Aero Glass, but nobody's currently using that since it involves setting environment variables before you launch Firefox.

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!