Meet the browser: Firefox Next


Recommended Posts

The_Decryptor
5 hours ago, JUANMAS7ER said:

To be fair, almost all browsers look like a Chromium iteration these days. There's not a big feature that makes them apart from each other (at least visually) untill someone comes with any

When Firefox initially was released one of the criticisms was that it looked too much like IE6 (And that it "stole" tabs from Opera). All browsers feed off each other (They all do the same job) and it shouldn't be surprising, a good UI design idea is still a good idea, and will get adopted.

 

3 hours ago, Demz said:

wonder if Mozilla will release a Preview Releases of it before its officially released to the public

Like in a nightly build or beta release?

Link to post
Share on other sites
bawz
2 hours ago, The_Decryptor said:

When Firefox initially was released one of the criticisms was that it looked too much like IE6 (And that it "stole" tabs from Opera). All browsers feed off each other (They all do the same job) and it shouldn't be surprising, a good UI design idea is still a good idea, and will get adopted.

 

Like in a nightly build or beta release?

no, something like a UX kinda Preview Release , i would think if Mozilla want Extension Devs to stay there gonna have to release something to allow the Extension devs something to work with, same as Themes i guess

but this is Mozilla, i dont have much faith in Mozilla nowadays

Link to post
Share on other sites
The_Decryptor

WebExtensions is already in stable Firefox, they don't need any special preview build.

 

Themes iirc are re-using the "LWT" model which Firefox has used for ages, not full blown themes but with the changes they want to make to the UI they wouldn't really cross over anyway (Themes are XUL, the new Firefox UI isn't)

 

Edit: Not really sure I agree with them completely removing full blown themes (they might make a comeback in the future), but in the near term no theme would cross over without an entire re-write anyway, so they can use it as an excuse to make a nicer theming API that won't hurt end users ("Safe Mode" shouldn't need to be a thing, that's the whole reason Mozilla is making these changes).

Link to post
Share on other sites
margrave

The removal of full blown themes was when I left FF.

Link to post
Share on other sites
BooBerry
Quote

 

Mozilla has just audited Tab Mix Plus in order to figure out what part of it functionality is possible to implement using WebExtensions:
https://bugzilla.mozilla.org/show_bug.cgi?id=1333837#c9

It looks like the fate of Tab Mix Plus WebExtension depends on these three bugs right now:

hiding the default tab toolbar - https://bugzilla.mozilla.org/show_bug.cgi?id=1332447
re-implementing tab toolbar using Toolbar API - https://bugzilla.mozilla.org/show_bug.cgi?id=1215064
styling individual tabs - https://bugzilla.mozilla.org/show_bug.cgi?id=1320585


I want Tab Mix Plus to survive so much :oops:

 

 

  • Like 5
Link to post
Share on other sites
BooBerry

ARM Opens Up Compute Library With OpenCL & NEON Acceleration

More details on the now MIT-licensed ARM Compute Library via ARM.com while all the code is over on GitHub.

 

  • Like 5
Link to post
Share on other sites
BooBerry

Photon Mock up of the changes to Customize mode as part of the upcoming design refresh

 

ljjlqb4.jpg

 

 

 

There is some discussion about that here. As I understand it, they aren't going for a separate development branch, and most changes will land gradually as they are ready. The more noticeable ones might be behind prefs or build system trickery.

  • Like 6
Link to post
Share on other sites
BooBerry
  • So it seems that flexible spaces are returning
  • Search bar is not going away! (but probably disabled by default?)
  • You can't customize the menu anymore, but only put buttons on the toolbar or in the overflow menu?
  • Like 5
Link to post
Share on other sites
BooBerry

Looking at the mock up (yes I know a lot could change by the time FF 57 lands on Release), it seems to me that the devs are creating empty space on the left side of the URL bar, and (possibly) forcing users to click on an overflow icon to access icons that no longer fit on the right side

If you remove that empty space, then the only time you would be forced to use the overflow icon is when you have resized the window to be too tiny. So then exactly the same behaviour you have in FF right now.

  • Like 5
Link to post
Share on other sites
bawz

THE search bar WILL BE IN A new tab, JUST LIKE chrome's OR THE ACTUAL SEARCH NOW WILL BE IN YOUR address BAR/lOCATION bar. JUST LIKE chrome's 

still hope you'll be ble to remove the dumb Pocket icon

Link to post
Share on other sites
bawz

as i stated above, your Search will be in the Address/Location Bar look at this Pic

Link to post
Share on other sites
bawz

so there wont be any Search Box near the address Bar like we have in Firefox now.

Link to post
Share on other sites
BooBerry
34 minutes ago, Demz said:

so there wont be any Search Box near the address Bar like we have in Firefox now.

2589mvm.jpg

  • Like 5
Link to post
Share on other sites
bawz

okz, but it aint there by Default

like it is in Firefox currently

Link to post
Share on other sites
BooBerry

n6mRHw4.png

 

 

 

bpwxcVo.png

 

 

4Req605.png

 

 

 

So looks like they are going to merge bookmark, history and download panels.

The main problem right now is bookmarks now taking two clicks to get to (three+ clicks to fully use). That's a really annoying increase for a feature that's likely used very often. I didn't see a bookmarks button in Customize either.

Edited by Lyraull
  • Like 7
Link to post
Share on other sites
BooBerry
Quote
  • DOM.  In the DOM team there are several plans and projects under way which will hopefully bring various performance improvements to the browser.  Probably the largest one is the upcoming plans for cooperative scheduling of tasks, which will allow us to interrupt currently executing JavaScript on background pages in order to service tasks belonging to foreground pages.  You may have seen patches landing as part of a large effort to label all of our runnables.  This is needed so that we can identify how to schedule tasks cooperatively.  We are planning to also soon do some work on throttling down timeouts running in background pages more aggressively.  More details will be announced about all of these projects very soon.  Furthermore we are working on smaller scale performance improvements in various parts of the DOM module as new performance issues are discovered through various benchmarks.
  • JavaScript.  In the JavaScript team there have been several streams of work ongoing to work on various improvements to the various aspects of our JS execution.  Jan de Mooij and colleagues have been running the CacheIR project for a while as an attempt to share our inline caches (ICs) between the baseline and Ion JIT layers.  This helps with unifying the cases that can be optimized in these JIT layers and has been showing meaningful improvements both on real web pages and benchmarks such as Speedometer.  They have also been looking at various opportunistic optimizations that also help performance issues we have identified through profiling as well.  Another line of investigation in the JS team for a while has been looking into this bug.  We have some evidence to suggest that our JIT generated code isn’t very efficient in terms of the CPU instruction cache usage, but so far that investigation hasn’t resulted in anything super conclusive.  Another extensive discussion topic was GC scheduling.  Right now the way that our GC (and cycle collection) scheduling works is pretty dis-coordinated between SpiderMonkey and Gecko, and this can result in pathological cases where for example SpiderMonkey sometimes doesn’t know that a specific time is an unfortunate time to run a long running GC, and Gecko doesn’t have a good way to ask SpiderMonkey to stop an ongoing GC if it detects that now would be a good time to do something else, etc.  We’re going to start to improve this situation by coordinating the scheduling between these two parts of the browser.  This is one of those architectural changes that can have a pretty big impact also in the longer term as we find more ways to leverage better coordination.  Another topic that was discussed was improving the performance of our XRay wrappers that provide chrome JS code access to content JS objects.  This is important for some front-end code, and also for the performance of some Web Extensions.
  • Layout.  In the Layout team, we are focusing on improving our reflow performance.  One challenge that we have in this area is finding which reflow issues are the important ones.  We have done some profiling and measurement and we have identified some issues so far, and we can definitely find more issues, but it’s very hard to know how much optimization is enough, which ones are the important ones, and whether we know of the important problems.  The nature of the reflow algorithm makes it really difficult to get really great data about this problem without doing a lot of investigation and analysis work, and we talked about some ideas on what we can do to improve our work flows, but nobody seemed to have any million dollar ideas.  So at the lack of that we won’t be waiting for the perfect data to arrive and we’ll start acting on what we know about for now.  Through looking at many reflow profiles, we have also developed some “intuitions” on some patterns on the types of expensive things that typically show up in layout profiles, which we are working on improving.  There are also some really bad performance cliffs that we need to try to eliminate.
  • Graphics. In the Graphics team, we are planning to make some performance improvement to display list construction by retaining and incrementally updating them instead of reconstructing them every time.  This is an extremely nice optimization to have since in my experience display list construction is the bottleneck in many of the cases where we suffer from expensive paints, and it seems like we have telemetry data that confirms this.  The graphics team is also looking into doing some optimizations around frame layer building and display list building based on measurements highlighting places where things could be improved.

 

  • Like 6
Link to post
Share on other sites
Steven P.
13 minutes ago, Lyraull said:

The main problem right now is bookmarks now taking two clicks to get to (three+ clicks to fully use). That's a really annoying increase for a feature that's likely used very often. I didn't see a bookmarks button in Customize either.

This annoys me with Chrome too (which is what I use) yes, there are extensions for it, but they almost all don't look great and don't feel native to the browser.

 

Chrome still misses easy access bookmarks (without resorting to the "bookmarks bar") and a address bar download manager (using this atm)

  • Like 2
Link to post
Share on other sites
BooBerry
Quote

 

 

 

Edited by Lyraull
  • Like 6
Link to post
Share on other sites
BooBerry
19 minutes ago, Steven P. said:

This annoys me with Chrome too (which is what I use) yes, there are extensions for it, but they almost all don't look great and don't feel native to the browser.

 

Chrome still misses easy access bookmarks (without resorting to the "bookmarks bar") and a address bar download manager (using this atm)

It is currently two clicks to use a bookmark -- Toolbar button > choose bookmark

With the library the process is three clicks -- Toolbar button > Bookmarks > choose bookmark

hope they give us a dedicated browse bookmarks button

 

there still is going to be a search box! and it seems like you can make the location bar full width if you remove the flexible spaces

and some negative is mostly not being able to customize the main menu.

  • Like 5
Link to post
Share on other sites
bawz

whoever is designing firefox need to be shot or HUNG,  but i know there mockups atm but hell, its one Fugly Browser , hate to say it, but it makes Chrome look better

Link to post
Share on other sites
bawz

RIP Firefox, Great knowing you or using you before you turned to ****

Link to post
Share on other sites
Konstantine
3 hours ago, Demz said:

RIP Firefox, Great knowing you or using you before you turned to ****

Yo, excuse me for the way I'll speak, but can you stfu already? Every comment of yours tilts me(and I'm sure other members). This negativity is not worthy my time checking this thread for info or a decent conversation. Thanks.

  • Like 3
Link to post
Share on other sites
Boo Berry

The mockups are really not that bad at all, actually. I've seen way, way worse.

  • Like 3
Link to post
Share on other sites
+Zlip792
2 hours ago, Boo Berry said:

The mockups are really not that bad at all, actually. I've seen way, way worse.

Probably from Stephen Horlander at time of Australis. :-p

  • Like 1
Link to post
Share on other sites

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
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By indospot
      Mozilla is worried about being collateral damage in Google's antitrust case
      by João Carrasqueira



      Yesterday, the United States Department of Justice filed an antitrust lawsuit against Google, accusing the search giant of monopolistic practices to maintain its dominant position in the search market. Among the practices brought up in the case is the fact that Google pays to be in the default search engine on some devices and web browsers, such as Mozilla Firefox.

      In response to the lawsuit, Mozilla has issued a statement regarding the accusations. The blog post opens by saying that Mozilla believes that scrutiny of these practices is important in order to "build a better internet".

      However, the organization follows up by bringing up the search agreement between Google and Mozilla, which allows Google to be the default search engine in Firefox. Mozilla says it's one of the organizations that's best positioned to drive competition on the web, and that the lawsuit shouldn't cause collateral damage to smaller and independent companies like Mozilla.

      Back in August, Mozilla and Google reportedly renewed their search agreement deal, which ZDNet estimated to be worth between $400 million and $450 million. This was shortly after Mozilla announced it would be laying off 250 employees as part of corporate restructuring, so it's apparent that Mozilla heavily relies on funding from this search agreement.

      Mozilla says it's still looking into the details of the lawsuit, and it will share updates on the case as more information comes. It'll be interesting to see if and how the lawsuit will be able to protect the interests of smaller organizations like Mozilla while putting a stop to Google's practices.

    • By zikalify
      Firefox 82 comes with a better picture-in-picture experience
      by Paul Hill



      Mozilla has begun rolling out Firefox 82 for users on the desktop. This update doesn’t come with very noticeable changes but does speed up the browser and includes a refined picture-in-picture experience that makes the feature easier to find for new users.

      Instead of the blue, nondescript, picture-in-picture button that appeared at the side of videos before, Firefox now shows a transparent grey box on the right-hand side of the video in the lower half that explains what the button is and what it does. After the user has had a chance to read the button it will be displayed as a circular button with the picture-in-picture icon. Even when it has shrunk to this form, the icon is larger than before making it easier to understand what it does.

      For users on Mac, picture-in-picture can be enabled by pressing Option + Command + Shift + Right bracket. This new command even works before the video starts so you don’t have to spend time waiting for the video to load before switching tabs. Firefox on Windows now uses DirectComposition for hardware decoded video which improves CPU and GPU usage while watching videos and improves battery life.

      Another big improvement in this update is the general speed of Firefox. According to Mozilla’s release notes, websites that use a flexbox-based layout load 20% faster than before, restoring a session is 17% quicker, and opening new browser windows in Windows is 10% faster. Mozilla’s WebRender has continued to roll out to more Windows users which will make browsing even faster for that group of people.

      Existing Firefox users on Windows and Mac should be automatically updated while Linux users will need to wait until their distribution maintainer pushes the latest packages. New users can go directly to the Firefox website and grab the latest software.

    • By Copernic
      Firefox 82.0
      by Razvan Serea



      Firefox is a fast, full-featured Web browser. It offers great security, privacy, and protection against viruses, spyware, malware, and it can also easily block pop-up windows. The key features that have made Firefox so popular are the simple and effective UI, browser speed and strong security capabilities.

      Firefox has complete features for browsing the Internet. It is very reliable and flexible due to its implemented security features, along with customization options. Firefox includes pop-up blocking, tab-browsing, integrated Google search, simplified privacy controls, a streamlined browser window that shows you more of the page than any other browser and a number of additional features that work with you to help you get the most out of your time online.

      What's new in Firefox 82.0:

      With this release, Firefox introduces a number of improvements that make watching videos more delightful the Picture-In-Picture button has a new look and position, making it easier for you to find and use the feature. Picture-In-Picture now has a keyboard shortcut for Mac users (Option + Command + Shift + Right bracket) that works before you start playing the video. For Windows users, Firefox now uses DirectComposition for hardware decoded video, which will improve CPU and GPU usage during video playback, improving battery life. Firefox is faster than ever with improved performance on both page loads and start up time: Websites that use flexbox-based layouts load 20% faster than before; Restoring a session is 17% quicker, meaning you can more quickly pick up where you left off; For Windows users, opening new windows got quicker by 10%. You can now explore new articles when you save a webpage to Pocket from the Firefox toolbar. WebRender continues to roll out to more Firefox users on Windows. Fixed:

      Screen reader features which report paragraphs now correctly report paragraphs in Firefox instead of lines. Various security fixes Changed:

      Credit card auto-fill is now more accessible with the card type, and the card number in the card editor now available to screen readers. Printing dialog errors for invalid form entries are now reported to screen readers. Developer:

      Developer Information MediaSession API has been enabled by default which allows web authors to provide custom behaviors for standard media playback interactions, giving them more options than ever. DevTools now shows server side events in the Network panel. This allows a server to send new data to a web page at any time allowing developers to see events they previously couldn't and help with lower-level troubleshooting. Download: Firefox 82.0 for Windows | Firefox 64-bit | ~50.0 MB (Freeware)
      Download: Firefox 82.0 for Linux | 64-bit | ~70.0 MB
      Download: Firefox 82.0 for MacOS | 73.1 MB
      View: Firefox Home Page | Release Notes

      Get alerted to all of our Software updates on Twitter at @NeowinSoftware

    • By Abhay V
      Microsoft releases Flight Simulator patch version 1.9.5.0 with a bunch of fixes
      by Abhay Venkatesh



      As promised last week, Microsoft has released a new patch for Flight Simulator, bringing version 1.9.5.0 to all users. Today’s update contains a bunch of fixes and improvements to various areas such as the UI, airports, planes, and more. The changelog also notes that multiplayer has been deactivated in the Japan discovery flight.

      While the patch notes are short – in comparison to earlier patches –, the download from the Store is a 569MB package, with the in-game content download size reaching 2.4GB. The company is quick to add that these notes do not include “every single item that was updated”. Regardless, fixes for the VFR screen causing game crashes and issues in the Avionics screens will be welcome additions for those who have been experiencing them. There are other fixes for auto-generated scenery.

      Here is the complete list of fixes in patch version 1.9.5.0:

      Interestingly, the company has not listed if the ‘Press any key to start’ prompt has been removed from the game. The firm listed this ‘Top wishes’ item as fixed and slated for release in the fourth update, which is what today’s patch is. Another item in the latest Feedback Snapshot denoted as fixed in ‘Update 4’ is the issue with the left engine failing to start on the A320, which also isn’t present in the release notes.

      In addition to the patch notes, the company has also updated the list of known issues and the possible workarounds. These include issues with various aircraft, airports, weather, and more. Users can head here to read through all the known issues and workarounds.

    • By Abhay V
      Apple releases watchOS 7.0.2 with fixes for battery drain issue and ECG app availability
      by Abhay Venkatesh



      Apple released iOS 14, iPadOS 14, watchOS 7, and tvOS 14 to supported devices in September, earlier than it usually would have, due to the pandemic and delays in announcing the iPhone line-up for this year. The updates brought significant changes for Apple’s offerings, including a design overhaul to the home screen in iOS that introduced an App Library for all apps, new widgets and much more. watchOS 7 was also a major release, finally bringing sleep tracking, support for third party watch faces, and more.

      Just a week after the release, the first bug-fixing update for the OSes came on September 24 and brought fixes to the default apps issue on iOS and iPadOS. Today, Apple is releasing the second bug-fixing update for the Apple Watch OS, bumping up the software to watchOS 7.0.2. The release brings improvements to battery usage and a fix for the ECG app not showing up.

      Here’s the complete changelog:

      While the update itself is fairly minor, the improvements to battery drain and the ability to enable the ECG app for users in regions where the feature is supported will be a welcome addition. However, more fixes and features are on their way in watchOS 7.1, which is currently in beta.

      Source: 9to5Mac