This commit adds an option to disable the tab-counter feature:
mcf.tabcounter.disable
Also, adding an option to also count tabs in the tab menu with
mcf.tabcounter.countmenu

We also opt to not show the tabcounter in convergent mode at
widths over 900px (beyond the Fairphone 5 in landscape mode).

Styling:
- make sure the enabled tab-counter is never rotated
- adding a rounded border to make it look somewhat native

Documentation:
Mention and document disabling the feature in README.md

Peter Mack authored 5 months ago and Oliver Smith committed 5 months ago

Fix #42 by adding a boolean about:config (mcf.multipletabs) option to reduce
tab width.

Fix #34 by adding another boolean about:config option
(mcf.multipletabs.showclose) to show close buttons on every tab.

gnumdk authored 8 months ago and Oliver Smith committed 5 months ago

Looks like original code was added this to keep the "all tabs" button visible.

This is not true anymore so we can put a min/max width for tabs.

We can also keep maximum width for non-private mode.

gnumdk authored 8 months ago and Oliver Smith committed 5 months ago

We are on a mobile device.

The next tracking feature where I assume every user wants to opt out.
https://support.mozilla.org/en-US/kb/privacy-preserving-attribution

This cuts down the private browsing indicator to a minimum
by hiding the text and removing some padding.

No longer hard remove Google from Firefox ESR, so it can be picked
as default if people want to/have to, e.g., due to ddg being blocked
in some regions.

https://cast.postmarketos.org/episode/39-Interview-magdesign/
inspired this.

popups.css: fix to prevent extension menu flicker on distributions that are not postmarketOS (MR 48)

Peter Mack authored 1 year ago and Oliver Smith committed 1 year ago

popups.css: Fix various popup menus and installing extensions, including a fix for the overflow menu (MR 47)

Peter Mack authored 1 year ago and Newbyte committed 1 year ago

Closes https://gitlab.com/postmarketOS/mobile-config-firefox/-/issues/63

Peter Mack authored 1 year ago and Oliver Smith committed 1 year ago

Based on user0's work, I've implemented a slightly different fix for
this menu:

* max-width only, because that's enough to fix the menu
* 100% instead of 100vw, as that's less in most cases, but enough.

Related: https://codeberg.org/user0/mobile-config-firefox/src/commit/f2381fd45eeef10ffb173a56f8106e6d68b981be/src/userChrome/06_popups.css#L85-L89
Fixes: #65

Prevent the user from installing to the wrong firefox dir, and give a
userfriendly message if install needs root rights.

Make it easy for users to test versions from a git repository by having
an easy way to uninstall.

Fix the pattern not working in neovim's now built-in editorconfig
support by removing "**/". This should have matched all paths, but it
doesn't work with the built-in parser and by removing it, we apparently
match all paths too. This fixes neovim indenting with tabs in the
Makefile and shell scripts in this repository.

Happy to see that this is a built-in feature now \o/

mobile-config-firefox does not need to support versions prior to the
oldest supported FF ESR release (there might be two at the same time).
The current oldest ESR is 115. Remove related code.

As time of writing, it is 120 and ESR 115.

As suggested by Robert Mader in issue 57, thanks.

Thanks to plata-gl for pointing this out. Fix #61.

Ulrik de Muelenaere authored 1 year ago and Oliver Smith committed 1 year ago

This fixes one of the issues from #52, but I have not been able to
reproduce the others on Phosh.

Ulrik de Muelenaere authored 1 year ago and Oliver Smith committed 1 year ago

Since Firefox 104 the Services global is available automatically and no
longer needs to be imported, and since Firefox 117 importing it is an
error.

Previously the Firefox version would be detected as 0 on the first
start, causing popups.before-ff-108.css to be included even on newer
versions, which breaks touch input.

Ulrik de Muelenaere authored 1 year ago and Oliver Smith committed 1 year ago

Firefox 113 changes from 'display: -moz-box' to 'display: flex', so the
-moz-box-flex property should be changed to flex-grow. However, that
breaks the tab menu, and it doesn't seem to be necessary anyway.

Ulrik de Muelenaere authored 1 year ago and Oliver Smith committed 1 year ago

Without this fix, the tab menu is only tall enough for 2 or 3 entries.

This is an update of the rule directly above it, changing the ID and
changing from a calculated height to a fixed height matching its child
#allTabsMenu-allTabsView. With the calculated height, the menu entries
were offset above the top of the menu. The previous rule no longer seems
to be necessary, at least in Firefox 102 and newer, since
#allTabsMenu-multiView does not exist.

Ulrik de Muelenaere authored 1 year ago and Oliver Smith committed 1 year ago

Firefox 113 changes from 'display: -moz-box' to 'display: flex', so we
need to use the order property instead of -moz-box-ordinal-group.