desktop: can't open new tabs
Captchas
- I have read the instructions.
- I have searched existing issues and avoided creating duplicates.
- I am not filing an enhancement request.
What happened?
can not open new tabs. Both new tab button and ctrl+t bring up the url bar.
Reproducible?
- I have checked that this issue cannot be reproduced on Mozilla Firefox.
Version
1.7.6b
What platform are you seeing the problem on?
Windows
Relevant log output if applicable
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 19
- Comments: 81 (14 by maintainers)
What an absurd design choice !! i have a speed dial set to new page (which i paid for) which now doesn’t come up. The URL bar is there all the time, if i want to use it, i clicked new tab as thats what i want! … Im not changing the config file to remove it, i’ll change browsers before i do that. Also, above it says press new tab then enter and it doesn’t do anything.
put zen.urlbar.replace-newtab to false in about:config
That’s the new default behaviour in Zen, as per release notes.
I feel like a thing like this should be a toggle in the settings as opposed to having to hunt for the exact flag in config. I understand the design decision, but I doubt this will be a very popular change.
Why do they change a lot of default behaviors with every single release? It would be better to keep the current behavior as it is and let everyone choose whether they want to try the new feature.
Can this “feature” be disabled? I really liked the new-tab pages because they included useful information like weather, news, recently visited websites etc.
If you hit your keyboard-shortcut that was previously opening a new-tab page, it now focuses the address-bar, empties it and whatever you search for or select gets opened in a new tab when you hit
enter. Your current tab and it’s address-bar remain untouched.This is NOT the same as simply typing something in the URL bar. It achieves the same result as the prior workflow, just skipping the opening of an empty/new-tab page.
The only people losing something with this are this are those having content on their new-tab page they want to see or interact with or toolbars only visible on their new-tab page.
Everyone else gets a faster, more efficient and smoother experience.
Yes, ideally it should be a normal setting and not change behavior for existing users, but changing a single toggle in
about:configis trivial and solves all your troubles.The workaround that @AlexandruJR posted works flawlessly. Thank you, this is a live saver. A new tab page is part of my workflow and it’s one of the things that’s important to me. This really needs to be a setting that is easily found. Even if you insist on having it buried in the advanced about:confic section, would I ever think to look at zen.urlbar.* when my new tab button does not open a new tab? I think that this move away from new tabs, which have been the standard across most browsers can be considered a paradigm shift and something of that magnitude requires more than just a single line in a changelog.
That being said, just I have to explain (or vent) how bad this feature has been implemented/rolled out in my opinion. It going to be ramble-y but I hope that the well intentioned feedback leads to positive change.
First, why would you have:
and then set it up so that none of these distinct things can even open a new tab? A new tab may be opened eventually by making the address bar behave inconsistently but it requires more user input after I already told the browser that I would very much like a new tab.
Second, you also give users the ability to install addons that change the behaviour and look of new tabs and none of them work with “zen.urlbar.replace-newtab” being enabled, which is the default. Why are you making changes that break extensions by design? At the very least, ask the user first.
Third, we give Microsoft a hard time whenever Windows updates change settings that the user had previously configured. I - and I suspect others too - will give you a hard time too if you change my settings without asking. I consider this hostile behaviour though others may be more forgiving.
Forth, if you want to change the default look and feel and the default behaviour of Firefox you can do that; Just because you’re Firefox based does not mean that you are Firefox. But at the very least - after asking the user if they want their settings changed - make it so that the change doesn’t make the UI misleading (or outright lying): Why does neither the new tab button nor the new tab shortcut open a new tab? If I wanted to focus the address bar, I could just do that instead of clicking the button or shortcut labelled “new tab”. You should also make it so that UI behaviour stays consistent. With the new “zen.urlbar.replace-newtab” feature enabled, the address bar sometimes opens addresses in the current tab and other times in a new tab. No indicator anywhere for which behaviour the user is going to get. You just need to know exactly how the address bar came to be focused. You can’t tell at a glance. As far as I’m concerned, this is a clear UX issue that needs to be resolved. It’s neither calmer nor does it feel like my experience is being considered.
Fifth, why would you label the update “another stability update while we are figuring big changes out” when in fact this is not a stability update but one of the big changes you’re claiming to still be figuring out? That was the first sentence in the release notes. I did not expect a new feature and thought I broke something with an extension or a setting I changed in about:config. While I’m on the release notes: They state that new tabs have been removed yet I can, with the “zen.urlbar.replace-newtab” feature enabled, open as many new tabs as I want. It’s rather easy: Click the new tab button (or ctrl + t) and type any address: a new tab opens. Do I really have to read every release notes page in full for every single update going forward just in case you decide to make a huge paradigm shift?
With all this being said: If the feature is not ready yet (it plain does not work the way any rational user would expect, it’s made the browser’s behaviour inconsistent, plus you’re “still figuring it out”, as you said yourselves), why is it in a regular release? Do you not have nightly builds for this? In the future, please:
And whatever you do, don’t go changing any of my preferences without asking me first!
I don’t intend for any of this to be read as hostile. Granted, I am irritated because I’ve just spent an hour trying to fix my browser because I thought that I somehow broke the new tab button and maybe I didn’t hide that irritation very well in my text - but this irritation is temporary. As a fellow developer/IT guy I know developing is hard and I know new features and milestones are exciting. But I always hope that there’s room for improvement and a little time to consider before pushing the release out the door.
EDIT: After reading that a lot of people have either seen or missed some kind of notification, I have now updated Zen Browser on a different device running Linux which had an earlier version of Zen installed, just like my Windows machine. On that Linux/KDE device I saw that a system notification has been created regarding the removal of new tabs. KDE probably lets you configure this, but on my Linux device, notification stay up until I dismiss them myself, Windows auto-hides them after a few seconds and I generally ignore them once hidden because of all of the unnecessary MS bloat in there. Why does MS tell me all the time that I don’t have viruses? I suspect many people keep missing the notification on their (Windows) machines because they don’t pay attention to that particular corner of their main screen - I oftentimes have my browser open on a secondary monitor. Also, there’s this option to run Zen when your computer boots: How many people turn on their computer, go make themselves a cup of tea/coffee and then come back to sit down with Zen already open and the notification long hidden or gone? And if there’s another kind of pop-up that tells users about the change, I did not see it, even on my second device when I was actively looking for it. To be clear: I’m not pointing fingers here! I would never have thought about system notifications at all and I dread to think what kinds of things I’d forget to consider if anyone ever put me in charge of a such a rollout. These things happen and the new behaviour is easy enough to revert once you know what you’re supposed to be looking for. Maybe for future releases, a system notification alone may not be enough for inattentive users such as myself?
This is bad. If it hadn’t been for the workaround, I’d have uninstalled it.
That’s the thing, I want people to have it on by default. To be given the opportunity to give it a try. If it’s off, no one will ever use it, because people dont like changes, even if it’s for their better. Im just very tired rn, all people have done today is shout at me.
I can’t do much anyways, the damage has been done. Ill just keep it like this and suffer the rest of the mad people
It’s nonsensical and I provided reasons why.
Yes, we all know it is in beta, we get that. It seems that what you aren’t getting is that big changes like this should be optional and disabled by default! Your production might have “increased insanely” and that’s great, I’m happy for you but mine hasn’t - it’s quite the opposite for me and that’s why I’m here - to give feedback. I’m not here to push a FOSS to it’s fucking limits… (your words)
Here’s an idea:
Rename “Firefox Labs” to “Zen Labs” and add options to new/experimental Zen features (with feedback options). Then notify users that new experimental features are available and that they can try them out and give feedback. That way you have users trying them out without crippling the browser for others.
Speaking of notifications, that popup you boast about displayed for a split second before disappearing.
Yeah, well. That’s just part of the process, because we are going from “stock firefox” to “something people arent use to”. But people not even giving it a try is the saddest part. My productivity has increased INSANELY with this change, due to less content shifting and less distractions / extra steps when searching or going to a new site. Sad people wont even truly experience it.
But I dont know, it’s a weird situation. Arc users are praising it, such as this was the last remaining feature to switch from arc for most of them. And firefox users are annoyed because it’s outside of their comfort bubble. That’s what im getting out of this
@mauro-balades maybe your productivity has “increased insanely”" but clearly not everyone’s has. I tried Arc and ditched it for that and many other reasons. I gave your change a go for a full day (so I did give it a chance), but honestly it’s awe full. Wanting a browser that is different is commendable, but one that breaks everyone else’s workflow, but not just yours is not. People will abandon zen if it doesn’t do the basics right. Nobody wants to go messing around in config to fix that which shouldn’t need fixing, every time there’s an update. I too use a group dial extension, as it’s a very quick way to get to a page I need since the top row of bookmarks is limited in width
Please give users the option in settings as a reasonable way to get the best of both worlds
I’ll stick with your project, because I believe you have done some fantastic work, and wish to continue to see how this matures. Despite the backlash. As with all projects of this nature these things will happen, and it’s really the consensus that should be considered. Most people will just leave without even coming here, so you may not fully see the impact, but word of mouth is everything.
please keep up the good work.
Might I add that this is completely unintuitive behaviour, if i can’t differentiate between opening a new tab and making a simple search, that’s a UX problem
Alr, this is getting annoying. Please keep issues just for bug reporting.
Please read: https://www.reddit.com/r/browsers/comments/1ik2o3n/comment/mbkc671/?utm_name=web3xcss as to why this decision has been made and it’s better for productivity enhancement. Maybe the “beta” text on the homepage isn’t big enough, might have to change that. It’s crazy to see such reactions. I dont want zen to just be yet another browser with the exact same things, for that, use chrome. Imagine apple if people told them to not innovate.
Guys, you are shouting to a wall right now. It’s not going to be changed back
This breaks functionality for anyone who has a custom new tab homepage (using an extension like New Tab Override). There should at the very least be an easily accessible setting for this in the settings menu, and better visibility of breaking changes like this that change core browser functionality. Currently it’s not clear unless you go digging for it as the keyboard shortcut to “open a new tab” has not changed name, and it does in fact not open a new tab when pressed (Ctrl+T default). Feels awkward.
This has to be silliest hill to die on. Why are we arguing about the supposed productivity boosts and benefits of the new approach, when no one is actually mad about the feature being added, just how it was added.
I’m sure some people will love the new way of managing new tabs, but you can’t just upset decades of expected behavior (in a PATCH release) for what is essentially personal preference and then be surprised that people are mad.
Does this project not follow semver? does the
1.7.6bjust exist for vibes? can we expect more breaking changes in another release that says “Another stability update while we are figuring big changes out!”?I like using zen and I will continue to use it, but I will no longer update the browser with confidence. I will never again blindly agree to automatic updates, nor will I recommend it to others while its in beta.
I dont think a regression is the solution either though. Maybe once I finish redesigning the settings modal I can add better visibility to this preference
Feedback of my own experience : I was very confused by the fact that my “New Tab” button don’t work anymore. Like some people on this thread, I had no warning popup so I first searched in the settings to see if something has changed but saw nothing. Then I thought my installation of the browser had a problem and I uninstalled/reinstalled it. Then I created a workaround with a “about:newtab” bookmark which is a “New tab button” with a middle click. I just found this issue page after googling what I thought was a bug.
Opening new tabs is a central part of a browser, changing it so suddenly should be an opt-in option or at least have a very easy way for opting-out. Even as a beta software, it’s still a very brutal move.
While I do agree that this could be handled a little bit better. It’s still under heavy development, whether the audience is big or not, I can’t control that. The moment you download it you are accepting the implications of using beta software.
As zen develops it’s identity, the idea of making one correct workflow keeps growing. In other words, if you aren’t using it how it is by default, you are using zen wrong. The browser market is filled with such bad ideas and anti-productivity market and the worse part is that they are normalized. That’s the whole point. If you are going to disable Zen’s features, what’s the difference between zen or brave? or chrome?
This whole convo could be a literal equivalent of asking apple if the traffic lights could be more “windows like”
I don’t like this approach of pushing stuff that doesn’t work… I know that is a beta browser but if you tell that this update is a “stable version” I want stable stuff…
As Dev and user, i want to contribute via positive feedback by giving some advice:
I don’t disagree that it can be annoying, but on my update it gave me a little notice with a disable button, and tbf you did install a beta.
There’s a few things I want to say:
1st of all, there’s nothing on the Zen website describing the browser’s aim being productivity-focused. It’s about a calmer, less cluttered experience, with the emphasis on the browser’s look.
2nd, yes, it’s a beta. A publicly available beta. Which means, to me, new features will be added in a more complete state than this was in order to garner feedback and bug notices. This feels like something barely out of the conceptual stage. Being a beta does not make the project immune from criticism. Quite the opposite. We’re speaking up now because, presumably, it’s easier to adjust things now than after actual release.
3rd yes, people have given it a chance. If we didn’t, we wouldn’t be complaining about it.
4th how is it even supposed to work? On 1.7.6b on MacOS, if I type in a URL into the address bar, it doesn’t open a new tab at that address. It just navigates that tab to the new address. Is that intentional? Is it only with search that it creates a new tab? If so, why?
5th, because of that kind of confusion, you really needed to communicate specifically how the new status quo is supposed to work. Something more substantial than “use the address bar.”
6th, again, accessibility. Yes, Ctrl/Command T opens a new tab. However, for someone like me with actual physical deformities in my hands because of Muscular Dystrophy, using a mouse or trackpad to open a new tab was always much easier for me. The browser is now much less accessible, and there should be a real option in settings to change it back rather than an about:config flag (which also speaks to point 2).
7th, all of this makes me wonder if you’re actually designing with more than you and your developer cohort in mind. Again, this change speaks far more to the “never have your hands leave the keyboard, I use Hyprland and Neovim” programmer crowd than those merely looking for a more generalized browser experience aimed at being aesthetically appealing.
Have you done any actual research? Do you know how many people use/prefer a specific new page tab over those who don’t (again, not counting yourself or fellow devs who represent a niche population)? Did you ever even consider the accessibility ramifications? Did you test the change with other people before releasing it?
8th, the website speaks of the browser being customizable down to the last pixel. If you’re going to be making changes to a browser’s workflow that we’ve all grown accustomed to over the last 20 or so years, then there needs to be options available to bring it back to a more universally recognized state (reiterating most of the above).
You mentioned Apple and innovation. Apple has had some of the best UX designers and engineers in the business work for them. The key to their innovation is that they base their designs around intuitive interaction. Tapping, swiping, etc are all natural, universal gestures. And when that doesn’t suffice, they have a plethora of settings that can be tweaked in order to give the user the experience that’s most comfortable and natural to them. What Apple tries to avoid is invalidating the ways in which people interact with similar devices/systems in the past. And they do a lot of research and iteration.
9th my suggestions are to slow down. Release new features only after they’ve been well-tested behind the scenes. Use actual semantic versioning. Have option toggles in settings (maybe a dedicated beta options section). Communicate changes clearly, with better instruction on how to use the new thing and what expectations are. Do real UX research beyond a programmer’s workflow. Keep accessibility in mind. Figure out what you really want Zen to be, because this change doesn’t neatly fit the project’s stated goals.
Good luck. Despite my criticism, I do want this browser to succeed. More non-chromium browsers available, the better IMO.
P.S. RE: point 6 - this comment took me over an hour to type, but I felt it was worth doing.
ctrl+thas become muscle memory to open new tabs. Since this update, I thought I had pressedctrl+las I couldn’t tell the difference visually.Physically disabled user here. This change absolutely makes the browser much less accessible for those of us who can use a mouse or trackpad better than a keyboard.
Change for the sake of change is bad design, especially when it needlessly removes core functionality that has been with tabbed browsers from the outset.
I do not like this change.
I do not like the default behavior changing for my browser every week in the morning when I start it.
These changes need to be SETTINGS that are not on by default. I absolutely should not have to fish around in about:config to go back to the way things were.
Until the philosophy around Zen changes, I won’t be using it any more.
This would be great if the popup stayed on my screen for longer than 0.2 seconds before navigating elsewhere
PLEASE stop changing defaults, make a popup that informs about new behaviour and asks us to OPT IN if we’re migrating from old versions.
Throwing in my 2c: this is a bad design decision. Even after having read the release notes and seeing there was mention of a change like this, I was very confused by the behavior at first. I don’t understand what users gain by not having a new tab page. You should make it opt-in, offer it to users in the first-run wizard and add a checkbox for it to settings.
Forcing something which seems like a developer’s personal preference then giving them an opt-out that involves modifying
about:configjust seems silly.I came here expecting to find a fix for an obvious bug, only to find a fix for intended behavior - nonsensical behavior I might add.
Not really sure what the thinking was here… Clicking on new tab opened up a new tab, focused the Search/URL bar (allowing for keyboard support) and provided you with other options like recently visited, bookmarks or add-ons/speed dials - I’m pretty sure this way of doing it catered to most if not all users.
But the new behavior? It feels like a regression in functionality… Clicking on new tab focuses the Search/URL bar (allowing keyboard support) and only opens up a new tab after typing in an address or search, providing you with no other options like recently visited, bookmarks or add-ons/speed dials - it’s on by default, no setting available and once again can only be turned off in about:config.
This should be configurable in settings and disabled by default. Just my two cents.
All I’m going to say is that the big button that literally says “+ New Tab” doesn’t open a new tab anymore. I mean, it does, but with an extra step… which is weird to me because before IIRC it opened a new tab and focused the URL bar anyway. So all you’ve really done is reverse the order of the new tab behavior, making it something unfamiliar.
Which, fine, whatever. Trying new things is neat. I remember when CTRL-Click made a sorta preview pop up instead of a new tab, and I liked that, so trying out new stuff can be good.
But this one makes custom new tabs really hard to use. The number of custom new tab addons available alone is an indicator that people use new empty tabs. I don’t really, but I liked the weather widget, and I set my bookmarks toolbar to only appear on the new tab page. So even though I don’t use a custom new tab page, this has affected my workflow.
I think the issue is that this is a BIG workflow change that comes kind of out of left field. I could adapt to it, I suppose, but I don’t find it to be particularly intuitive. It’s not bad, it’s just unnecessary and makes customization harder.
I do wish people would be a bit kinder in their responses on both sides, though. We’re all in this together, and if it’s made you made enough to curse or get sarcastic with developers who are doing all this work for free, maybe try out the vertical tabs in Firefox Nightly, or Floorp, or Firedragon.
you have to search for something and it will open up in a new tab. i agree it is a bad choice. if you know any other firefox basted browsers with vertical tabs please tell us.
Zen is one of the most ridiculous projects ever. I like the browser itself, but every single release changing default behaviour to some stupidity no one really wants is tiresome. Adding new options is good, but instantly making them default is just plain stupid. I almost believe that the sole purpose of Zen is to troll users.
New tab looks great with a bit of css. I don’t care if you change the default, but please keep the option in the settings rather than hiding it in about:config. I would have uninstalled it if it weren’t for the workaround, because I love having the chill wallpaper between tabs with my most used pages just one click away. It’s like a game savepoint between pages, I’d go crazy without it.
I came here to figure out how to turn this off, and make it work the way it makes sense to work. I was onboard with sticking with Zen. But this response you put out, made me change my mind. I get so sick of this idea of “we know whats best so do it our way” holier than thou attitude. Good luck in your endeavor, I sure hope you make new users to compensate for those you pissed off and pushed away today. You are going to need all the luck you can get if you keep going this route.
Stop saying it’s nonsensical, I literally linked the whole reason this was added 😭
I don’t know how many times I have to say the same fucking message over and over again, that it’s on beta stage. It’s insane how the community can push a FOSS to it’s fucking limits. We know what’s best for the project, we know what we want to do with zen (create a difference in the market). If these blank comments with no actual value keep appearing on this thread ill just lock it.
There’s no profit here, there’s no big corp trying to use you as a product. We are just a group of passionate developers experimenting in such a boring market. This isn’t an airport, you dont have to state if you are leaving or entering.
How is it unfinished? Has been tested through weeks and didn’t have any bug reports yet. I still find it incredible such reaction for having a product developing on it’s self, just go use chrome if you dont like it, no one’s forcing you. But there’s no need to start chaos in reddit, github, etc
My guy, you are literally using beta software…of course things will change a lot until it hits stable.
Isnt that what the URL already does?! but now my speed dial doesn’t work. couldn’t name one benefit of adding this “feature”. updates should add functionality, not remove it. There is one i just found called floorp, and it does appear to have vert tabs, haven’t fully investigated yet though. hopefully they change this back
I am getting pretty close to dropping Zen over stuff like this. This seems like a very poorly received change that was forced on people with no straightforward way to disable it (going to github issues to find what about:config flag to change is not straightforward). And all I seem to see is people doubling down on the decision like it is the same thing, but it isn’t.
Aside from not being able to easily access the new tab page that most people are used to. The “new tab address bar” doesn’t even behave like a normal address bar. For instance when using the address bar of an actual tab (new or otherwise) I can type “google” and press ctrl+enter and it gets automatically changed to “google.com” when loading (I have been using this behavior with every major browser for the last 20 years). With this new address bar, instead it opens a new tab that is a duplicate of my current tab and has nothing to do with what I typed. Almost any other behavior would be more intuitive.
god bless you my saver of the day ❤️
https://github.com/user-attachments/assets/f3975fcb-67b1-49b7-bddf-bc6e962db9ea
why not just have them up here?
Had to delete 20 posts today. The change can be reverted, it has been announced everywhere and a popup appears at your screen when updating. So I don’t understand what’s the problem?
I understand not wanting to be different, but I don’t think this is necessarily innovation. Easy to use and factoring in workflows is what it’s about. But if this is the philosophy behind Zen, then I will be leaving it behind.
true, the default should be what everyone is used to
Yeah I just assumed this was a bug!
I glanced at the release notes and could not have imagined that note meant that something as commonly used as Ctrl+T would not work as expected.
I think Zen trying new things is a feature not necessarily an issue - but maybe it would be helpful to come up with a more in your face way to warn people about something like this after an update and how to revert it. Or since this is configured with a feature flag, let people opt into it on their own!
glad i could help ❤️
The problem with the supposed big button that keeps getting mentioned is that it only flashes for less than half a second for most people. so we end up missing that. Plus, a new feature that disrupts 99% of peoples workflow should have an easier method for disabling instead of having to search google and find out that it can only be done in about:config. Which was fine 20+ years ago but is unacceptable in 2025.
Yeah, a popup that lasts less than a second.
This issue is you changed a very standard behaviour to something that’s also not intuitive. If I click “new tab” I want a new tab. Not the address bar. Having it as an option is great but this is going to confuse anyone trying out the browser just like it clearly did with people already using it. And if you do that consistently that will ensure this browser never becomes popular. This could easily have been an option in the already existing dropdown which selects behaviour for new tabs. It was luck I came across this thread because I honestly thought it was either a bug or unfixable. The latter would have made me leave
It should be named
zen (beta)i fix this 1 - Open the ‘about:config’ 2 - ‘zen.urlbar.replace-newtab’ false 3 - Open the ‘New Windows and Tabs setting’ from setting and change 'Firefox Home (Default)
For the record, I don’t think anyone here is saying it’s wrong to support it at all. We’re saying to keep it as an official option but not change defaults. If people have set their own, let them keep it as is, but inform them there’s a new way to do something, and keep it available in general settings.
Constant changes to my workflow are exhausting as I keep things set up for my own use. Having to constantly fix these upsets is a time investment and actually causes me more downtime than it does speed up my workflow.
This popup alone is bugged for me! It only shows up on pages that are loading. Not when i try to click new tab, not when I navigate. I was looking at it before Zen redirected me to the patch notes page and I immediately looked in settings to try and revert it, because this isn’t what I want. Only to find it’s not there, and the only places I can see it – and STILL see it after disabling it in about:config. It’s physically not present on screen long enough to even interact with.
I’m not looking to be forced to try something new – ironically forcing me to try it is a surefire way to make me reject it. Providing the option however, may get me to consider it – I don’t appreciate agency being taken away is the thing, and I feel that’s true about a lot of people – especially provided that this browser features extensive customizability.
Small nitpick, but I didn’t even see any popup communicating this change, which might be why so many people are this confused. Had to check GitHub to understand why there was no new tab. I only saw a small notification on the bottom right for 1 frame when switching tabs, and it was gone, no way to see what it said, nothing in the logs. (fedora 41 flatpak if relevant)
I use it as a collection of recent pages/weather. Basically a small hub to launch into where I need to go
Firefox Nightly https://blog.nightly.mozilla.org/2024/08/07/firefox-sidebar-and-vertical-tabs-try-them-out-in-nightly-firefox-labs-131/
Im honestly just tired of them constantly changing behavior of the browser in large ways without an obvious way back its so stupid that I need to go into about;config so much. I love the browser but this is the only one I’ve needed to go to a github for because they want to change entire workflows with no way back
Ehhh!! Wrong! having to go into about:config is not trivial, it is dumb. New changes should not be implemented unless there is a toggle for you to opt-in for it. Or at least to make it easier to opt-out. NO ONE IN 2025, SHOULD HAVE TO GO INTO about:config.
Couldn’t find the setting to turn this off in the main settings…
The notification to disable the feature only flashes for a second because sites load too fast for me to even interact with it. So I used a VPN and picked the worse ping I could find just so I could interact with the box… and the “disable” button doesn’t even work…
With a project name like “zen”, I sure do wish the namesake design philosophy was used. Constant changes that are not fully thought through and visual bugs on almost every release causes more frustration than productivity.
@jcf278 please stick to only bug reports, dont add useless messages as they send notifications to everyone
Ridiculous choice, this shows to me how this project is in fact strange… I had uninstalled it thinking it was a bug, and now I find out it was a dev choice, incredible. Will not install it again.
In this thread I see people who are okay with reverting the change with their about:config, frustrated about the change happening suddenly, or deciding the browser is not for them.
I’m going to be honest the primary reason I used zen was for split tabs, it was Hyprland like and FireFox based which improved working on git repos. I don’t need anything else.
We ALL have our own workflows we’re efficient in, and the idea of one true workflow, in my opinion, does not exist. Facilitating customization to support multiple workflows, is key to a broad usability base. It feels more to me like you’re building your perfect workflow but not accounting for the other users who use your application.
I understand making a personal project like that, and I respect it! But if that’s the direction you wish to take Zen, I wish you the best luck! I think our workflows simply do not align.
I use speeddial and yeah this is super annoying. I feel like the devs change things for no reason at all with updates which makes it really annoying to use this browser long-term. Stop changing core functionality. Nobody had an issue with how it worked before and if you ARE going to change something, make it an option for US to turn on.
After I turned on my computer and launched Zen, I also got that popup – but it disappeared after less than 3 seconds because Zen immediately opened the release-notes website.