<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Firefox 161 breaks custom themes AGAIN. Stop all the unnecessary layout rewrites that break our work and give users nothing in return. in Discussions</title>
    <link>https://connect.mozilla.org/t5/discussions/firefox-161-breaks-custom-themes-again-stop-all-the-unnecessary/m-p/147042#M60298</link>
    <description>&lt;P&gt;On behalf of everyone who builds themes, userChrome styles and extensions for Firefox: please &lt;STRONG&gt;STOP&lt;/STRONG&gt; shipping renames and layout rewrites that break our work and give users nothing in return.&lt;/P&gt;&lt;P&gt;Firefox 161, due November 24, is the latest example. One bug (&lt;A href="https://bugzilla.mozilla.org/show_bug.cgi?id=2074327" target="_self"&gt;2074327&lt;/A&gt;) does two things:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;It rewrites the container tab line AGAIN. Nova restyled the 2px container line in Firefox 158. Three releases later it has been rebuilt from scratch: the line is now absolutely positioned and its sizing variables were replaced. My theme draws the line on the tab's right edge; in 161 it lands on the left.&lt;/LI&gt;&lt;LI&gt;It renames the container color variables with no fallback. --identity-stroke-color became --identity-color, and --identity-fill-color was deleted. Every theme that set those variables silently stopped recoloring containers. In mine, the container colors in the address bar, menus, sidebar and Firefox View all fell back to Nova's palette.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Although the line rewrite does fix some real issues, it also highlights a larger problem: Nova went out with a container line people had already reported as broken, and fixing it now breaks everyone who adapted to it. The rename fixes nothing a user can see.&lt;/P&gt;&lt;P&gt;This is the pattern, not an exception. Between the 160 release and today's Nightly, 159 of Firefox's built-in stylesheets were added, removed or changed, about 6,000 lines. tabs.css alone has had 80 commits since August 20, twelve of them reverts. With a new release every two weeks, anyone who styles Firefox spends their time chasing renamed variables instead of building anything.&lt;/P&gt;&lt;P&gt;Real fixes are not the issue. The same release scrolls the address bar so a spoofed domain can't hide behind the overflow fade (&lt;A href="https://bugzilla.mozilla.org/show_bug.cgi?id=1598175" target="_self"&gt;1598175&lt;/A&gt;, open since 2019), and it exposes the fade width as a variable themes can use. That is how a change should be made. The complaint is about churn nobody asked for.&lt;/P&gt;&lt;P&gt;"userChrome.css is unsupported" is not an answer. People use it because Firefox keeps removing options, and when an update breaks it, users don't blame the theme, they blame Firefox.&lt;/P&gt;&lt;P&gt;I think speak for most developers and advanced users in requesting the following:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Keep renamed CSS variables as aliases for several releases, and announce when they will be removed.&lt;/LI&gt;&lt;LI&gt;Don't rewrite how a UI element is built unless users get a visible benefit from it.&lt;/LI&gt;&lt;LI&gt;Finish designs before they ship instead of reworking the same element release after release.&lt;/LI&gt;&lt;LI&gt;Publish a short list of theme-facing variable and selector changes with each release.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Bottom line: Firefox claims that it lets people make the browser their own. Every pointless break undercuts the claim and it's extremely frustrating.&lt;/P&gt;</description>
    <pubDate>Thu, 12 Nov 2026 11:29:26 GMT</pubDate>
    <dc:creator>ffbug</dc:creator>
    <dc:date>2026-11-12T11:29:26Z</dc:date>
    <item>
      <title>Firefox 161 breaks custom themes AGAIN. Stop all the unnecessary layout rewrites that break our work and give users nothing in return.</title>
      <link>https://connect.mozilla.org/t5/discussions/firefox-161-breaks-custom-themes-again-stop-all-the-unnecessary/m-p/147042#M60298</link>
      <description>&lt;P&gt;On behalf of everyone who builds themes, userChrome styles and extensions for Firefox: please &lt;STRONG&gt;STOP&lt;/STRONG&gt; shipping renames and layout rewrites that break our work and give users nothing in return.&lt;/P&gt;&lt;P&gt;Firefox 161, due November 24, is the latest example. One bug (&lt;A href="https://bugzilla.mozilla.org/show_bug.cgi?id=2074327" target="_self"&gt;2074327&lt;/A&gt;) does two things:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;It rewrites the container tab line AGAIN. Nova restyled the 2px container line in Firefox 158. Three releases later it has been rebuilt from scratch: the line is now absolutely positioned and its sizing variables were replaced. My theme draws the line on the tab's right edge; in 161 it lands on the left.&lt;/LI&gt;&lt;LI&gt;It renames the container color variables with no fallback. --identity-stroke-color became --identity-color, and --identity-fill-color was deleted. Every theme that set those variables silently stopped recoloring containers. In mine, the container colors in the address bar, menus, sidebar and Firefox View all fell back to Nova's palette.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Although the line rewrite does fix some real issues, it also highlights a larger problem: Nova went out with a container line people had already reported as broken, and fixing it now breaks everyone who adapted to it. The rename fixes nothing a user can see.&lt;/P&gt;&lt;P&gt;This is the pattern, not an exception. Between the 160 release and today's Nightly, 159 of Firefox's built-in stylesheets were added, removed or changed, about 6,000 lines. tabs.css alone has had 80 commits since August 20, twelve of them reverts. With a new release every two weeks, anyone who styles Firefox spends their time chasing renamed variables instead of building anything.&lt;/P&gt;&lt;P&gt;Real fixes are not the issue. The same release scrolls the address bar so a spoofed domain can't hide behind the overflow fade (&lt;A href="https://bugzilla.mozilla.org/show_bug.cgi?id=1598175" target="_self"&gt;1598175&lt;/A&gt;, open since 2019), and it exposes the fade width as a variable themes can use. That is how a change should be made. The complaint is about churn nobody asked for.&lt;/P&gt;&lt;P&gt;"userChrome.css is unsupported" is not an answer. People use it because Firefox keeps removing options, and when an update breaks it, users don't blame the theme, they blame Firefox.&lt;/P&gt;&lt;P&gt;I think speak for most developers and advanced users in requesting the following:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Keep renamed CSS variables as aliases for several releases, and announce when they will be removed.&lt;/LI&gt;&lt;LI&gt;Don't rewrite how a UI element is built unless users get a visible benefit from it.&lt;/LI&gt;&lt;LI&gt;Finish designs before they ship instead of reworking the same element release after release.&lt;/LI&gt;&lt;LI&gt;Publish a short list of theme-facing variable and selector changes with each release.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Bottom line: Firefox claims that it lets people make the browser their own. Every pointless break undercuts the claim and it's extremely frustrating.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Nov 2026 11:29:26 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/firefox-161-breaks-custom-themes-again-stop-all-the-unnecessary/m-p/147042#M60298</guid>
      <dc:creator>ffbug</dc:creator>
      <dc:date>2026-11-12T11:29:26Z</dc:date>
    </item>
  </channel>
</rss>

