Recommended Posts

I can't believe that mozilla removed version numbers of addons from the main addons page: 

 

firefox-addon-manager-no-versions.jpg

 

I have updated the "classic theme restorer" to the latest beta build which lets you bring it back. I hope mozilla sees some sense and brings it back or at least gives us a setting in about:config to re-enable it.

I can't believe that mozilla removed version numbers of addons from the main addons page: 

 

firefox-addon-manager-no-versions.jpg

 

I have updated the "classic theme restorer" to the latest beta build which lets you bring it back. I hope mozilla sees some sense and brings it back or at least gives us a setting in about:config to re-enable it.

On what version? I run Firefox beta at work and see the version numbers.  Your screenshot looks like have a small window open and is not full screen. Regardless, why does it even matter? It looks cleaner and better to me... I am sure it says the version if "click" on more or options.

 

EDIT: Nevermind, I missed it says Nighty. You realize that means nothing right? They play with a lot ideas that never make it to the stable channel.

On what version? I run Firefox beta at work and see the version numbers.  Your screenshot looks like have a small window open and is not full screen. Regardless, why does it even matter? It looks cleaner and better to me... I am sure it says the version if "click" on more or options.

 

EDIT: Nevermind, I missed it says Nighty. You realize that means nothing right? They play with a lot ideas that never make it to the stable channel.

That screenshot is from nightly, i'm running firefox 40 beta 1 and it has no version numbers either.

That screenshot is from nightly, i'm running firefox 40 beta 1 and it has no version numbers either.

My bad, I did try to update my comment before you replied. Changes in Nighty mean nothing and why is this a big deal again?

I can't believe that mozilla removed version numbers of addons from the main addons page: 

 

firefox-addon-manager-no-versions.jpg

 

I have updated the "classic theme restorer" to the latest beta build which lets you bring it back. I hope mozilla sees some sense and brings it back or at least gives us a setting in about:config to re-enable it.

I fail to see why the version numbers matter, it shows them if you open the addon details anyway.

I fail to see why the version numbers matter, it shows them if you open the addon details anyway.

Because obviously the old Firefox UI was perfect, and change == bad. Look at how he as configured the browser as an example.

Because obviously the old Firefox UI was perfect, and change == bad. Look at how he as configured the browser as an example.

Yeah, he has installed lots of addons which make the browser sh**ty, laggy and ugly. If 50-100 people out of all Firefox users do it, it's still not enough. That proves they don't like change and their taste is the same as the browser's look they have achieved after so many addons. Period

 

Edit: Firefox's current UI is beautiful, amazing and easy to use. It can't be compared to the old one(where the orange Firefox button was placed top-left) as well as to Chrome or Opera. I like Edge's simple UI, but Firefox's one is top.

Firefox 40 beta has been released and here is the full release notes --> https://www.mozilla.org/en-US/firefox/40.0beta/releasenotes/

 

  • New

    Support for Windows 10 including tablet mode

 

No reason for Windows 10 users to be on the stable channel (or anyone) and with 64-bit support.

All they mean is that Firefox can now detect tablet mode (MS didn't make it easy), not that it runs like a Store app in tablet mode.

Even the latest nightly doesn't have Win10 tablet mode fixes in it yet.

.... is there an article on this?

Not that I'm aware of, it's all going in a bit a time. Best way is to follow the main bugs about it.

Bug 1158143 is the bug for theme changes, Bug 1170714 is for tablet mode support (Bug 1170522 was the changes for letting Firefox know about tablet mode) and Bug 1077146 is the overall bug with Win10 work.

Does this indicate that Mozilla will be in Win Ten Store?

EDIT: https://bugzilla.mozilla.org/show_bug.cgi?id=1163607

"Prepare Firefox for integration in the Windows store"

Dis is good

Edited by _Alexander

Why not? Win Ten is gong to arrive in a month.

Huh? I don't know what you are trying to say... Firefox 39.0 does not have support for Windows 10 tablet mode nor a 64-bit version. I am just saying FF users are better off on the beta channel.

All they mean is that Firefox can now detect tablet mode (MS didn't make it easy), not that it runs like a Store app in tablet mode.

Even the latest nightly doesn't have Win10 tablet mode fixes in it yet.

Why would I want or need Firefox to be a store app? I would rather them spend their resources getting 64-bit and e10s to stable.

Windows 64-bit binaries and e10s landing in stable is still a ways off.

Everything I heard was by fall or the end of year. The original time table for 64-bit was like spring/summer. It's becoming ridiculous as everyone and their bother has a 64-bit browser now.

Why would I want or need Firefox to be a store app? I would rather them spend their resources getting 64-bit and e10s to stable.

I meant that existing store apps are all XAML and such, and support full screen mode because they run on Windows 8.

That said, store apps are the future with the changes MS made in 10, 99% of apps can gladly run as store apps and users will benefit (They can be sandboxed, they've got automatic updates, etc.).

I meant that existing store apps are all XAML and such, and support full screen mode because they run on Windows 8.

That said, store apps are the future with the changes MS made in 10, 99% of apps can gladly run as store apps and users will benefit (They can be sandboxed, they've got automatic updates, etc.).

Thanks for the Microsoft marketing promo... Win32 programs work just fine right now, FF already gets automatic updates, and I have no security concerns. It seems to me a win32 program running in a hypervisor would result in a performance hit. Yes? No?

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

    • I have been using Firefox for years.
    • I'd trust open source stuff on github more then closed source binaries from Microsoft.
    • OpenAI is now rolling out Lockdown Mode to more ChatGPT users by Pradeep Viswanathan Back in February, OpenAI first announced Lockdown Mode for users who want the most comprehensive protection from potential attacks. At the time of the announcement, the company mentioned that this feature was available to a small set of highly security-conscious users, including executives or security teams at leading organizations. Today, OpenAI announced that Lockdown Mode is now rolling out to all personal ChatGPT accounts, including Free, Go, Plus, and Pro, and also self-serve ChatGPT Business accounts. Users can enable the feature from ChatGPT Settings > Security when it is available for their account. When Lockdown Mode is enabled, ChatGPT limits or disables several features that connect to the web or external services. These include live web browsing, Deep Research, Agent Mode, and more. Here is the complete list of services that will be disabled in Lockdown Mode: Live web browsing: Web browsing is limited to accessing only cached content. Search results may be limited, unavailable, or stale. Image support: ChatGPT may not display images in regular responses or retrieve images from the web. Users can still upload image files, and image generation remains available where it is otherwise available. Deep research: Deep research is disabled. Agent mode: Agent mode is disabled. Canvas networking: Users cannot approve Canvas-generated code to access the network. File downloads: ChatGPT cannot download files for data analysis. ChatGPT can still operate on your manually uploaded files. It is important to note that Lockdown Mode does not completely block prompt injections from appearing in content that ChatGPT processes. For example, a malicious instruction could still be present in an uploaded file or cached web content. However, the mode is designed to reduce the ways such an attack could send sensitive information outside the conversation. Along with Lockdown Mode, OpenAI today also announced that the Active sessions feature is now available across ChatGPT accounts and workspace types. This feature allows users to review where their account is signed in across devices and end sessions if required. A session will have the following information displayed: Device or browser information. First-party app context, such as ChatGPT, Codex, or API Platform. Approximate location. Sign-in date and time. Whether the device is a trusted device. Whether it is your current session. OpenAI highlighted that the Active sessions feature will not be available for accounts linked to an organization’s single sign-on setup, including SAML or OIDC.
  • Recent Achievements

    • Rookie
      moog19 went up a rank
      Rookie
    • Mentor
      grik went up a rank
      Mentor
    • Dedicated
      JKR earned a badge
      Dedicated
    • One Year In
      CHUNWEI earned a badge
      One Year In
    • Conversation Starter
      FBSPL earned a badge
      Conversation Starter
  • Popular Contributors

    1. 1
      +primortal
      491
    2. 2
      PsYcHoKiLLa
      270
    3. 3
      Skyfrog
      75
    4. 4
      Steven P.
      68
    5. 5
      FloatingFatMan
      63
  • Tell a friend

    Love Neowin? Tell a friend!