Live data from Hacker News

How to make a better default Firefox UI

github.com

101–110 of 266 posts

Re: How to make a better default Firefox UI

#101
post #42
post #21

Earlier quoted context omitted.

Standard Firefox. >I'd image that firefox developers actually use it as their browser too.. The graphic design of Firefox is not made by developers, it's made by designers who don't use Firefox.

Citation needed, I'd say.

vdaea just said it

Re: How to make a better default Firefox UI

#102

Is anyone else not at all bothered by the tabs "being buttons"? I feel like I'm the only one sometimes. Are they really that jarring for first-time users?

I moved on to sideberry and hide the normal tab bar completely. But if you open two identical tabs in the default layout I have no clue which one is active anymore. You can't understand that UI, you have learn it. It's infuriating.

It doesn't render the one you clicked on in a different colour? That might be a issue with the theme you use, my firefox shows the active tab in a clearly different colour from the inactive one.

Re: How to make a better default Firefox UI

#103

Is anyone else not at all bothered by the tabs "being buttons"? I feel like I'm the only one sometimes. Are they really that jarring for first-time users?

I had exactly the same thought. I even installed the theme in question to see if I would like tabs better and honestly I prefer how Firefox does it stock.

Re: How to make a better default Firefox UI

#104
post #76

Earlier quoted context omitted.

It's corporate talk for "if it breaks, don't complain"

It's also a sneaky strategy to deal with features you've decided to remove, because users are that fucking stupid. 1. Instead of just removing the feature, hide the feature and call it unsupported so the users who remember the feature can't complain yet. 2. Then finally remove the feature in the next update, with justification that it was an unsupported option and used by few people, so users can't complain. Frog boi…

It can be metrics driven the whole way.

- Compact mode is rarely used and a pain to maintain

- If we hide the feature, what's the user reaction?

- Minimal user reaction to hiding, we're safe to remove

Re: How to make a better default Firefox UI

#105
post #76

Earlier quoted context omitted.

It's corporate talk for "if it breaks, don't complain"

It's also a sneaky strategy to deal with features you've decided to remove, because users are that fucking stupid. 1. Instead of just removing the feature, hide the feature and call it unsupported so the users who remember the feature can't complain yet. 2. Then finally remove the feature in the next update, with justification that it was an unsupported option and used by few people, so users can't complain. Frog boi…

[deleted]

Re: How to make a better default Firefox UI

#106

My greatest "unnecessary Firefox UI change gripe" is the removal of browser.urlbar.clickSelectsAll 4 years ago. And as you might expect, Mozilla does not care. If you read the bug report, this literally cannot be explained by anything except user hostility. https://bugzilla.mozilla.org/show_bug.cgi?id=1621570 Literally no other text field in any UI behaves like this. I cannot fathom why Mozilla chose to both ship thi…

And it's still broken, because the "Paste and Go" feature doesn't work.

Common sense suggests "Paste and Go" would be equivalent to using "Paste" (which correctly inserts text from the clipboard at the cursor position) followed by "Go to the address in the Location Bar." But if you unselect the automatically selected URL, position the cursor within it, then use "paste and go", Firefox ignores the previous URL and simply tries to go to the text in the clipboard. This could potentially be a security risk by tricking people into visiting URLs they didn't intend to.

If they don't want to fix this, it should be renamed to "Clear, Paste, and Go", because that's what it actually does.

Re: How to make a better default Firefox UI

#107

Earlier quoted context omitted.

That's very interesting, specially that telemetry is being used to justify removing interface items. In my opinion the address bar is so incredibly large you could put 10 buttons in there and you would still have space, so I can't imagine a reason to bother removing things besides wanting to remove everything until there is nothing you can remove left. You seem to be knowledgeable about UI/UX. May I ask you a questio…

In the middle of the article, there is a brief discussion about icons and colors. I also think that well-coordinated color icons are good for readability and usability. https://github.com/black7375/Firefox-UI-Fix/wiki/%5BArticle%... However, it is difficult to apply it universally to support a variety of colors. If it is similar to the background color, it is difficult to distinguish and there may be contrast issues…

Oh, I missed that. It's satisfying to see what I assumed to be true to be laid out so concretely as data points.

I just wish it was something more 3D and "skeuomorphic" instead of just making a flat gray arrow into a flat green arrow. For example, if Chrome used a yellow star instead of a white star outline, I bet a lot of people would say it looks ugly as hell and sticks out like a sore thumb, but I'd prefer it. I can barely tell these monochrome icons apart.

Re: How to make a better default Firefox UI

#108
post #76

Earlier quoted context omitted.

It's also a sneaky strategy to deal with features you've decided to remove, because users are that fucking stupid. 1. Instead of just removing the feature, hide the feature and call it unsupported so the users who remember the feature can't complain yet. 2. Then finally remove the feature in the next update, with justification that it was an unsupported option and used by few people, so users can't complain. Frog boi…

It can be metrics driven the whole way. - Compact mode is rarely used and a pain to maintain - If we hide the feature, what's the user reaction? - Minimal user reaction to hiding, we're safe to remove

If I recall correctly, that was their justification for no longer supporting it: too few people used it. Except it was tucked away in a small dropdown at the bottom of the customize toolbar screen, which requires right-clicking the toolbar to get to. If it was in the actual settings somewhere or, better yet, given as an option during the first launch flow, I imagine more people would've used it.

I didn't even know about it until after it became unsupported.

Re: How to make a better default Firefox UI

#110
post #98

Everyone is writing their pet peeves, so here are mine: * Having a large tree of bookmark folders, navigating it to add a new bookmark is horrible in the small pop-up that is the "Add Bookmark" UI. * The Bookmarks sidebar allows to search by name but not to find where they are. A bookmark search add-on (Bookmark search plus 2) solves this, but it shouldn't be needed. EDIT: I've been told about right-click -> Show in…

Do you perhaps have muscle memory for the Ctrl+Shift+B shortcut that used to open a large side panel but now just shows a narrow horizontal bar?

I do and I'm certainly annoyed by this redesign, but I discovered the "manage bookmarks" shortcut Ctrl+Shift+O that opens a larger pop-up window with your bookmarks, which so far seems almost as comfortable as the old side panel.

It also lets you search for bookmarks and right-clicking to select "show in folder" in the context menu shows you where in the hierarchy it is. (Though all my bookmarks are in "other bookmarks", so I don't expect to be using this much.)

Post reply on HN