{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihk56soeyncnmo2wpjt7x4x24xipxxol4zgwsvuxlpj7vakdj2vlm",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mjmg3loti462"
  },
  "path": "/viewtopic.php?t=32098&p=272394#p272394",
  "publishedAt": "2026-04-16T11:05:30.000Z",
  "site": "http://forum.palemoon.org",
  "tags": [
    "@Moonchild"
  ],
  "textContent": "> The problem here is that the decision whether to change (or not) the browser's UI, should be left to user. Not to extension icons.\n>\n> I like flexibility too but if any extension can happily break it, then there's no point. So, IMO some sort of hardening against extension icons is needed and ideally a few extra options to play with the Status Bar's height.\n>\n> I believe the Status Bar not getting affected by \"Use Small Icons\" is by design, but cannot be 100%. Only Moonchild can answer this stuff.\n>\n>\n>> I like the fact that the size of the buttons on the \"Status Bar\" isn't limited by a fixed height of this bar, so I don't like the idea of @Moonchild changing this behavior in the Pale Moon code. Instead, he could add an entry in \"about:config\" for the option to make the heights of the \"add-on bar + status bar\" fixed or flexible, depending on users' preferences.\n>\n> I like it too, but flexible should mean \"only allow the user the change it\", not \"allow any extension icon to break it\".\n\nIf @Moonchild changes the behavior of the \"Status Bar\" and \"Add-on Bar\" without adding an option to avoid this change (as you proposed in a previous comment), then this decision may satisfy you but will displease those who prefer my approach. However, if @Moonchild adopts the solution I proposed (adding an entry in \"about:config\" so the user can decide), then this solution will not conflict with your proposal if the option you prefer is set as default in \"about:config\". In that case, you won’t have to do anything to get the solution you want, while I’ll have to change the setting in \"about:config\".\n\n**********\n\nIn my previous comment, I said:\n\n\n> If code is added to the \"userChrome.css\" file, the height of the \"Status Bar\" is set by the code added to the bar with the ID \"status-bar\", but the size of the displayed image for this button (\"bypass_cloudflare_with_firefox_cookies_BUTTON.png\" 32x32 pixels) is scaled down only by the code added to the bar with the ID \"addon-bar\"\n\nIn fact, the height of the \"Status Bar\" can be adjusted without targeting the bar with the ID \"status-bar\" but by adding the same code to the bar with the ID \"addon-bar\". However, this approach is not a good one because it alters the position of the notifications displayed on \"Status Bar\".\n\n**Screenshots:**\n\n1. The position of notification displayed on \"Status Bar\" after adding the code to set the height of the bar with the ID \"status-bar\":\n\n\n2. The position of notification displayed on \"Status Bar\" after adding the code to set the height of the bar with the ID \"addon-bar\":\n\n\n* * *",
  "title": "Extension Releases/Support • Re: Bypass Cloudflare with Firefox Cookies",
  "updatedAt": "2026-04-16T11:05:30.000Z"
}