Recommended Posts

I tried installing Stylish but says it hasn't been updated to work with my version of firefox (latest beta).

https://addons.mozilla.org/en-US/firefox/addon/2108/

The above should work if you have add on compatibility reporter installed.

Is it possible to edit the spacer you can use in the customize menu?

there is "flexible space" & "space" to choose from.

I've used "space" here.

Have a look to see what i mean:

post-251611-12831617856436.png

post-251611-12831617884669.png

I have rounded corners in the nav.bar and want the "home" button more close to the edge

to suite the bar.

Maybe a little bit vague, but I hope someone understands :laugh:

Cheers

Anyone who wants to make a mockup like style , i am giving you a base code :)

Pic :

96245213.png

Code :

#appmenu-button dropmarker
{ margin: 0 1px 0 0 !important; }

#appmenu-button-container
{	position: fixed !important;
	top: -1px !important; }

#main-window[tabsontop="true"] menubar 
{	margin-left: 100px !important; }


#main-window[sizemode="maximized"][tabsontop="true"] #appmenu-button-container 
{	position: fixed !important; 
 	margin: 6px 0px 4px 4px !important;
 	top: 2px !important; }

#navigator-toolbox[tabsontop="true"] #TabsToolbar
{ padding: 22px 0 0 9px !important; }

#main-window[tabsontop="true"]
{ margin-top: -25px !important; }

.tabbrowser-tab[fadein]:not([pinned])
{ max-width: 200px !important; }

#appmenu-button {
 -moz-box-shadow: 0 0 2px 0 rgba(255,255,255,.75) inset,
 	0 1px 0 rgba(255,255,255,.45) inset !important;
 border: 2px solid !important;
 border-top: 0!important;
 -moz-border-left-colors: rgba(255,255,255,.5) rgba(83,42,6,.9) !important;
 -moz-border-bottom-colors: rgba(255,255,255,.5) rgba(83,42,6,.9) !important;
 -moz-border-right-colors: rgba(255,255,255,.5) rgba(83,42,6,.9) !important;
 max-height: 20px !important;
 min-height: 20px !important;
 background-color: rgba(255,255,255,1) !important;
 background-image: -moz-linear-gradient(rgba(244,172,17,.85),
 	rgba(218,107,17,1) 100%) !important;
 padding: 0 16px 1px 16px !important;
}

#appmenu-button:hover:not(:active):not([open]),
#bettermenu-button:hover:not(:active):not([open]) {
 background-image: -moz-linear-gradient(rgba(244,172,17,.70),
 	rgba(218,107,17,1) 100%) !important;
}

#appmenu-button:hover:active,
#appmenu-button[open],
#bettermenu-button[open] {
 -moz-box-shadow: inset 0 0 2px 0 rgba(0,0,0,.4) !important;
}

#TabsToolbar > .toolbarbutton-1:not(#alltabs-button):not(#new-tab-button) {
 -moz-appearance: none !important;
 margin: 0 !important;
 padding: 0 !important;
 background-repeat: no-repeat !important;
 background-size: 200% !important;
 -moz-border-image: url("chrome://browser/skin/tabbrowser/tab.png") 4 5 3 6 / 4px 5px 3px 6px !important;
 -moz-border-radius: 10px 8px 0 0 !important;
}

.tabbrowser-tab:not([selected="true"]),
.tabs-newtab-button,
#TabsToolbar > .toolbarbutton-1:not(#alltabs-button):not(#new-tab-button) {
 background-position: -5px -2px !important;
 background-image: -moz-linear-gradient(top,rgba(198,201,206,.70),
 	rgba(151,160,172,.70)),
 	-moz-linear-gradient(bottom, rgba(0,0,0,.8) 20%, rgba(0,0,0,0) 60%) !important;
}

.tabbrowser-tab:not([selected="true"]):hover,
.tabs-newtab-button:hover,
#TabsToolbar > .toolbarbutton-1:not(#alltabs-button):not(#new-tab-button):hover {
 background-image: -moz-linear-gradient(top,rgba(198,201,206,.8),
 	rgba(151,160,172,.8)),
 	-moz-linear-gradient(bottom, rgba(0,0,0,.8) 20%, rgba(0,0,0,0) 60%) !important;
}

.tabbrowser-tab:not([selected="true"]) {
 text-shadow: 0 1px 0 rgba(255,255,255,.3) !important;
}

I have rounded corners in the nav.bar and want the "home" button more close to the edge

to suite the bar.

Cheers

Code for rounded corners please!! :drool:

I'm not sure I follow what you mean by you, altered them, and now they don't show up.

The scripts I used were from userstyle.org and some from here. But I did not use the entire script of anyone of them. Just bits and pieces. I just put the CSS in userChrome.css manually. When I tried to install Stylish, it showed no scripts being installed. In order for them to show up in Stylish, I would have to remove everything I have and then install each script using Stylish and then edit the scripts. That is way too much work.

Here you go:

(don't remember where I got it from)

#navigator-toolbox[tabsontop="true"] #nav-bar {
	-moz-border-radius-topleft: 5px;
	-moz-border-radius-topright: 5px;
}

Thanks :)

I created a userstyle of the my above code and this rounded navigation bar code :D

http://userstyles.org/styles/36259?r=1283177010

The scripts I used were from userstyle.org and some from here. But I did not use the entire script of anyone of them. Just bits and pieces. I just put the CSS in userChrome.css manually. When I tried to install Stylish, it showed no scripts being installed. In order for them to show up in Stylish, I would have to remove everything I have and then install each script using Stylish and then edit the scripts. That is way too much work.

I see. Would just copying all the contents of your userchrome.css over to a single new stylish script work? Afterwards you can organize those bits and pieces into their own individual stylish scripts, one at a time, whenever you wanted.

This way you don't have to click a bunch of times and make a ton of individual new scripts just to recreate your current set up, you would be set with one script. But you would still have the capability to organize them later on when you feel like it.

I see. Would just copying all the contents of your userchrome.css over to a single new stylish script work? Afterwards you can organize those bits and pieces into their own individual stylish scripts, one at a time, whenever you wanted.

This way you don't have to click a bunch of times and make a ton of individual new scripts just to recreate your current set up, you would be set with one script. But you would still have the capability to organize them later on when you feel like it.

Thanks, I probably could do that but it may be against their TOS as the styles are a mosh of other users posted scripts. It is not a big deal, to not have Stylish. When Firefox 4 goes final, I may just start over again anyway.

Tabs in Titlebar

/* Move tabs up to titlebar in maximized window */

#navigator-toolbox[tabsontop=true] #TabsToolbar {

margin-top: -16px !important;

padding-left: 112px !important;

padding-right: 112px !important;

}

/* Move tabs up to titlebar in normal window */

#main-window[sizemode=normal] #navigator-toolbox[tabsontop=true] #TabsToolbar {

margin-top: -21px !important;

padding-left: 109px !important;

padding-right: 109px !important;

}[/code]

But if i show the menu with ALT Key, the tab shows overlapped with menu. Not nice...

Is there a way to change the height of the tabs? I recently downloaded a windows 7 theme and it put a blue bar on top of a black background. This would be perfect for the tab bar if the tabs didn't stick out above the blue bar. I just need to shrink the tabs by a few pixels but I have no idea where to start. Any help would be appreciated.

post-201025-12831924755856.jpg

Is there a way to change the height of the tabs? I recently downloaded a windows 7 theme and it put a blue bar on top of a black background. This would be perfect for the tab bar if the tabs didn't stick out above the blue bar. I just need to shrink the tabs by a few pixels but I have no idea where to start. Any help would be appreciated.

http://userstyles.org/styles/13709

The above userstyle may work for you.

Navigator Toolbar Shadows and Curved Corners (with work, could become the white underglow in the Office 2010 titlebar)

@namespace url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul);

/* Shadow above navigator toolbar, curved corners */
#navigator-toolbox[tabsontop="true"] #nav-bar {
    -moz-border-radius-topleft: 5px;
    -moz-border-radius-topright: 5px;
    -moz-box-shadow: 0px -3px 5px rgba(0,0,0,0.3);
}

How did you get it so that the shadow doesn't appear on the active tab?

Messing around with a few "clear" codes, anyone got a good one? Using a combination of Gary7 and Soapys, good, but not complete yet. Having problems with app tabs not aligning properly at the bottom, and also getting the history sidebar to look like the bookmarks sidebar in Gary7 code.

post-346088-1283298962378.png

How did you get it so that the shadow doesn't appear on the active tab?

The navigation toolbar is at a lower layer than the active tab (I think) so its box shadow is drawn below it.

Some script updates:

Here's what it looks like when you hit ALT (the tabs are now shifted down and the menu bar appears):

post-173518-12833005521623.png

Tabs in Titlebar (now the menu-bar is shown properly, instead of behind the tabs!)

@namespace url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul);

/* Move tabs up to titlebar in maximized window */
#navigator-toolbox[tabsontop="true"] #TabsToolbar {
    padding-left: 109px !important;
    padding-right: 112px !important;
}

/* Move tabs up to titlebar in normal window */
#main-window[sizemode="normal"] #navigator-toolbox[tabsontop="true"] #TabsToolbar {
    padding-left: 109px !important;
    padding-right: 109px !important;
}

/* Move the menubar above the tabs so it moves the tab bar down when activated */
#toolbar-menubar {
    margin: -19px 0px 3px 109px !important;
}

#main-window[sizemode="normal"] #toolbar-menubar {
    margin: -24px 0px 3px 109px !important;
}

Navigator Toolbar Shadows and Curved Corners (now has a sweet white underglow, Office 2010 style, when maximized!)

@namespace url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul);

/* Shadow above navigator toolbar, curved corners */
#main-window[sizemode="normal"] #navigator-toolbox[tabsontop="true"] #nav-bar {
    -moz-border-radius-topleft: 5px;
    -moz-border-radius-topright: 5px;
    -moz-box-shadow: 0px -3px 8px rgba(0,0,0,0.4);
}

/* White underglow above navigator toolbar */
#main-window[sizemode="maximized"] #navigator-toolbox[tabsontop="true"] #TabsToolbar {
    background-image: -moz-linear-gradient(top, rgba(255,255,255,0) 20%, rgba(255,255,255,1)) !important;
}

New App Button Margin Fixes

Now you can use Soapy's new app button out of the box, just add and modify this short script, which also moves the app button to the corner when maximized.

@namespace url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul);

#main-window[sizemode="normal"] {
    margin-top: -1px !important;
}

#main-window[sizemode="maximized"] #appmenu-button {
    margin-left: -3px !important;
    -moz-border-radius-bottomleft: 0px !important;
}

Just a note that due to the changes in the stylish code, it is now only compatible with tabs-on-top and a hidden menu-bar (the default Minefield configuration). I could probably fix this using more refined selectors, but the current script will work for now.

tabs on top for beta 5 with no firefox button.

@namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"); 
#navigator-toolbox[tabsontop="true"] 

#navigator-toolbox[tabsontop="true"] #TabsToolbar{
padding-left: 0px !important;
margin-right: 105px !important;
padding-top: 0px !important;
}

#appmenu-button-container {
position: fixed !important;
}

#main-window {
margin-top: -24px !important;
}

#appmenu-button{
padding: 3px !important;
-moz-border-radius-bottomleft: 0px !important;
} 

So I really liked some of the app button concepts that are being considered for the final release of Firefox.

Stephen Horlander even added patch code in bug 574681 to make it look like this:

post-173518-12834977372977.png

Which everyone on Bugzilla seems to like. I do too! So I've created a style out of it!

Firefox 4 App Button Style for Bug 574681 Patch 1.0 (for Windows XP, Vista and 7)

@namespace url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul);

#appmenu-button {
    -moz-appearance: none !important;
    background-image: -moz-linear-gradient(rgb(247,182,82), rgb(215,98,10) 95%) !important;
    -moz-border-radius: 0 0 4px 4px !important;
    border: 2px solid !important;
    border-top: none !important;
    -moz-box-shadow: 0 1px 0 rgba(255,255,255,.25) inset, 0 0 0 1px rgba(255,255,255,.25) inset !important;
    text-shadow: 0 0 1px rgba(0,0,0,.7), 0 1px 2px rgba(0,0,0,.5) !important;
    padding: .1em 1.5em .15em 1.5em !important;
    -moz-border-left-colors: rgba(255,255,255,.5) rgba(83,42,6,.9) !important;
    -moz-border-bottom-colors: rgba(255,255,255,.5) rgba(83,42,6,.9) !important;
    -moz-border-right-colors: rgba(255,255,255,.5) rgba(83,42,6,.9) !important;
    -moz-box-shadow: 0 1px 0 rgba(255,255,255,.25) inset, 0 0 2px 1px rgba(255,255,255,.25) inset !important;
}

#appmenu-button:-moz-window-inactive {
    background: transparent !important;
    background-clip: padding-box !important;
    border-color: rgba(0,0,0,.4) !important;
    -moz-border-left-colors: rgba(255,255,255,.4) rgba(0,0,0,.5) !important;
    -moz-border-bottom-colors: rgba(255,255,255,.4) rgba(0,0,0,.5) !important;
    -moz-border-right-colors: rgba(255,255,255,.4) rgba(0,0,0,.5) !important;
    -moz-box-shadow: 0 0 0 1px rgba(255,255,255,.25) inset !important;
}

#appmenu-button:hover:not(:active):not([open]), #appmenu-button:hover:-moz-window-inactive:not(:active):not([open]) {
    background-image: -moz-radial-gradient(center bottom, farthest-side, rgba(252,240,89,.5) 10%, rgba(252,240,89,0) 70%), -moz-radial-gradient(center bottom, farthest-side, rgb(236,133,0), rgba(255,229,172,0)), -moz-linear-gradient(rgb(246,170,69), rgb(209,74,0) 95%) !important;
    border-color: rgba(83,42,6,.9) !important;
    -moz-box-shadow: 0 1px 0 rgba(255,255,255,.1) inset, 0 0 2px 1px rgba(250,234,169,.7) inset, 0 -1px 0 rgba(250,234,169,.5) inset !important;
}

#appmenu-button:hover:active,
#appmenu-button[open] {
    background-image: -moz-linear-gradient(rgb(246,170,69), rgb(209,74,0) 95%) !important;
    -moz-border-radius: 0 !important;
    -moz-box-shadow: 0 2px 4px rgba(0,0,0,.4) inset, 0 1px 1px rgba(0,0,0,.2) inset !important;
}

Remember, this is a work in progress and is not reflective of the final UI. And remember to disable it when the patch finally does get committed!

So I really liked some of the app button concepts that are being considered for the final release of Firefox.

Stephen Horlander even added patch code in bug 574681 to make it look like this:

post-173518-12834977372977.png

Which everyone on Bugzilla seems to like. I do too! So I've created a style out of it!

Remember, this is a work in progress and is not reflective of the final UI. And remember to disable it when the patch finally does get committed!

Very nice but I'm not a fan of the inactive button style.

Very nice but I'm not a fan of the inactive button style.

You can remove it entirely by just removing the block of code marked by -moz-window-inactive

Previous button iterations haven't had this kind of effect. It takes a while to get used to, but I don't really look at inactive windows too hard anyway.

If it really bothers you, why don't you sign up at Bugzilla and make a suggestion? Maybe it'll make it into the next patch!

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

    • No registered users viewing this page.
  • Posts

    • AMD RX 9070 GRE AI, Blender benchmarks vs 9070 XT, 7800XT, Nvidia RTX 5070, 4070 by Sayan Sen Earlier this week, we shared the first part of our review of AMD's new RX 9070 GRE. It was about the gaming performance of the GPU, and we gave it an 8 out of 10. As a follow-up, similar to how we did with the 9070 XT and non-XT, we are doing a dedicated productivity review for the RX 9070 GRE as well, where we compare it against the 9070 XT, 9070, 7800 XT, as well as Nvidia's 5070 and 4070. This will include AI, rendering, compute, and more benchmarks. AI performance, especially, is a very important metric in today's world, and AMD also promised big improvements thanks to its underlying architectural improvements. We will be pitching it against the data we already have for the RX 9070, and RX 9070 XT, but also the Nvidia 5070 FE, MSI GeForce RTX 4070 VENTUS 2X 12G, and Gigabyte Radeon RX 7800 XT GAMING OC 16G as they are in a similar price class, but also because we do not have a comparable 5060 Ti card lying around here that we can compare it against. Before we get underway, this is a collaboration between Sayan Sen and Steven Parker, who lent me his test bed. Also, there was no editorial input from AMD. First up, the specs of the RX 9070, 9070 XT, and 9070 GRE, which were given to us by AMD: Radeon RX 9070 GRE Radeon RX 9070 Radeon RX 9070 XT Boost Clock: Game Clock: up to 2.79GHz up to 2.20GHz up to 2.52GHz up to 2.07GHz up to 2.97GHz up to 2.40GHz Stream Processors 3,072 (48 CU) 3,584 (56 CU) 4,096 (64 CU) Ray Accelerator 48 56 64 AI Accelerator 96 112 128 ROPs 96 128 Texture Mapping Units 192 224 256 Memory 12 GB GDDR6, 18Gbps Clock, 192-bit Bus 432 GB/s 16 GB GDDR6, 20Gbps Clock, 256-bit Bus Effective Memory Bandwidth: 640 GB/s Infinity Cache 48 MB (3rd Gen) 64 MB (3rd Gen) Card Bus PCI-E 5.0 X16 Output 2x HDMI 2.1b 2x DisplayPort 2.1a Power consumption 220W 304W Recommended PSU 650W 750W Slot width 2x 3x Price (SEP) $549 $599 As you can see from the specs above, it is less than the standard RX 9070 in every way that counts, except for slightly higher Boost and Game clock speed. Design Moving on, the RX 9070 GRE we were given is an XFX Swift triple-fan, dual-slot design with two 8-pin connectors. At 30cm (self-measured), it will fit in most systems easily. There is no RGB either. The AMD Radeon RX 9070 GRE by XFX from all angles. Test system Our test system consists of the following: Lian Li O11 Dynamic Mini V2 Flow (Amazon|Newegg) ASUS Z890 ProArt Creator WiFi (Amazon|Newegg) Intel Core Ultra 7 270K Plus (Amazon|Newegg) Thermal Grizzly KryoSheet - 44x37 (Amazon|Newegg) 2x 16GB G.Skill Trident Z5 RGB (7200 MT/s in XMP) (Amazon|Newegg) Sabrent Rocket4 Plus 2TB SSD (Amazon) Windows 11 25H2 (Build 26200.8246) AMD shared a press driver based on the recently released Adrenaline 26.5.2 that we were required to use. We now move on to our benchmarks. First up, we have Geekbench AI running on ONNX. For some reason, the 9070 GRE does exceptionally well here in both half-precision (FP16) and single-precision (FP32). It manages to beat the RTX 5070 and RX 9070 non-XT, and is only behind the 9070 XT. Since Geekbench runs in short bursts instead of continuously hammering the graphics card, it seems the GRE's faster boost clocks are helping here. Next up, we move to the UL Procyon AI test suite, starting with the image generation benchmark. We chose the Stable Diffusion XL FP16 test since it is the most intense workload available on Procyon. The Nvidia cards do very well here, as even the 4070 out-muscles AMD's best fairy easily. The positive thing about the GRE is that it gets quite close to the 9070 non-XT in this test; this indicates that the VRAM does not play a very big role here, as SD XL relies on float16 (FP16). So this is something to keep in mind again. If you wish to work with float32 AI workloads, graphics cards with larger than 12 GB buffers would likely emerge as victors. Regardless, the gains are still massive on AMD's 9000 series compared to the 7000 series. Following image generation, we move to the text generation benchmark. This is one test where the 9070 GRE struggled, quite a lot. It seems that the 12 GB VRAM and lower memory bandwidth of the new Radeon 9070 GRE are hurting it quite a bit; the split is massive, especially in a test like Llama2, which packs 13 billion parameters. As such, in all the tests, the 9070 GRE is the slowest of the lot. Next, we tried Blender, and here the AMD GPUs were beaten by Nvidia. Rendering is something the Green team has always had a lead over the Red side, and it has not changed so far. On the positive side, though, the 9070 GRE shows significantly better results than the 7800 XT, which means AMD is on the right path. Catching up to Nvidia, though, will require a lot more effort. And we hope HIP and ROCm can keep improving. Wrapping up AI testing, we measured OpenCL throughput in the Geekbench compute benchmark. The RX 9070 GRE alongside the 9070 did not fare well here at all, even falling behind the 7800 XT. Interestingly, even the RTX 5070 could not beat the 4070 on OpenCL, so perhaps this suggests that OpenCL optimization may not have been a priority for either AMD or Nvidia in the modern era. Conclusion We reached the end of our productivity performance review of the 9070 GRE, and we have to say it's a mixed bag. Unlike the 9070 and 9070 XT, the GRE excels in some areas while losing ground fairly easily in others. Similar to how it happened in gaming, any time the card's memory subsystem gets hammered, it tends to fall behind the others. This was the case with text generation, wherein we saw the VRAM sometimes hit its maximum available 12 GB of usage with larger model sizes. So what do we make of the RX 9070 as a productivity hardware? It can certainly be used, but you have to know it has its limitations. For those looking for a GPU that can deal with more, AMD recently unveiled the Radeon AI PRO R9700, which is essentially a 32 GB refresh of the 9070 XT with some additional workstation-based optimizations. On a similar note, the new Ryzen AI Halo platform is something you can consider if you want to set up a local AI processing station. Considering everything, we rate AMD's Radeon RX 9070 GRE a 7.5 out of 10 for its productivity performance. Price is less of a factor for those looking at productivity cases compared to those considering the GPU for gaming, and as such, we felt it did quite decently on many occasions and can be handy if you need a 12 GB GPU and, for some reason, don't want to get Nvidia. Purchase links: RX 9070 / XT / GRE (Amazon US) As an Amazon Associate, we earn from qualifying purchases.
    • Does anyone here know if these updates are integrated into the UUP dump isos?
    • Motrix Next 3.9.4 by Razvan Serea Motrix Next is a modern, open-source cross-platform download manager built as the official next-generation successor to the original Motrix project. It has been completely rewritten using Tauri 2, Vue 3, TypeScript, and Rust, while still relying on the powerful Aria2 download engine for high-speed multi-protocol transfers. The app supports HTTP, HTTPS, FTP, BitTorrent, ED2K and magnet links, offering advanced features like multi-connection acceleration, task scheduling, bandwidth control, and batch download management. With a significantly reduced install size (around 20MB), it focuses on being lightweight, fast, and resource-efficient compared to traditional Electron-based download tools. Designed for Windows, macOS, and Linux, Motrix Next delivers a clean, modern UI inspired by Material Design 3 principles, with smooth animations and a minimal workflow. It improves usability through better download organization, system tray integration, and enhanced torrent handling including selective file downloads and tracker management. Motrix Next features: Multi-protocol downloads — HTTP, FTP, BitTorrent, Magnet, .torrent, ED2K, and Metalink tasks BitTorrent — Selective file download, DHT, peer exchange, encryption controls, metadata caching, GeoIP peer flags, and tracker probing Browser extension integration — Embedded Extension API with independent authentication, download confirmation, smart auto-submit, filename hints, referer/cookie forwarding, and real-time controls (Chrome Web Store · Edge Add-ons) Safe filename handling — Content-Disposition, RFC 2047, non-UTF-8, percent-encoded, and extensionless URL resolution with path traversal sanitization Download organization — Favorite and recent folders, optional file-type categorization, stale-record cleanup, and completed history backed by SQLite Concurrent downloads — Independent controls for active tasks, HTTP connections per server, segments per file, and BT peer limits Speed control — Global and per-task upload/download limits with day-of-week and time-of-day scheduling System integration — Tray operation, optional tray speed display, macOS Dock badge/progress, protocol handlers for magnet://, thunder://, and motrixnext:// Lightweight mode — Destroys the WebView on minimize-to-tray while Rust keeps the engine, task monitor, notifications, history, and extension routing alive Notifications and power options — Native task start/complete/failure notifications, keep-awake during downloads, and optional shutdown after completion Network controls — Scoped proxy support for downloads, app updates, and tracker updates, plus system proxy detection Auto-update channels — Stable, Beta, and Latest Across Channels policies with separate download and install phases Diagnostics — Structured logs, exportable diagnostic ZIPs, database integrity checks, automatic DB rebuild, and Linux GPU rendering fallback Personalization — Light/dark/system theme, 10 color schemes, 26 languages, and first-launch system language detection Motrix Next 3.9.4 changelog: Motrix Next 3.9.4 promotes the 3.9.4 beta cycle to stable. This release refreshes bundled engine binaries, improves task detail readability and copy actions, expands link handling for magnet and ED2K workflows, polishes responsive navigation and text wrapping, updates browser extension documentation, and refines network preference controls. New Features Task Detail copy actions — Added copyable values for task metadata and reusable render functions for long text fields. Magnet and ED2K lifecycle support — Added task lifecycle handling for magnet and ED2K links. History cleanup for deleted tasks — Deleted tasks can now remove matching history records. User-Agent management — Added user-agent management and improved related network preference controls. Browser extension documentation — Added the Firefox Add-ons link for the Motrix Next extension. Improvements Engine binaries — Updated bundled binaries for supported architectures. Task Detail readability — Long task names, URLs, tracker values, and copyable metadata now render more clearly. Deletion messaging — Refined localized task deletion text for clarity and consistency. Text wrapping — Improved URI input wrapping and task name multiline display. Navigation layout — Improved sub-navigation responsiveness. Disk allocation default — Changed the default file allocation method to trunc. Proxy controls — Improved proxy button styling in network preferences. Download: Motrix Next 64-bit | ARM64 | macOS ~20.0 MB (Open Source) Links: Website | macOS / Linux | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • NVIDIA officially supports Ubuntu, as linked above with the GeForce NOW Hands on I did in collaboration with Paul Hill.
    • TO be clear I am not running linux today, however I keep thinking about it. And I want to make sure there are minimal obstacles if I decide to make that switch in the coming months.
  • Recent Achievements

    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
    • Dedicated
      Mark Spruce earned a badge
      Dedicated
    • Collaborator
      conkir earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      479
    2. 2
      PsYcHoKiLLa
      244
    3. 3
      Steven P.
      72
    4. 4
      FloatingFatMan
      66
    5. 5
      +Edouard
      66
  • Tell a friend

    Love Neowin? Tell a friend!