Recommended Posts

  • 4 weeks later...

There are problem with latest nightlies:

<snipped>

hope they are fixed soon :)

Seems fine here though on 64bit UX build 12.01a :/

You're sure that you aren't using any other addons?

Incompatible with Nightly 12.0a1, even with add-on compatiblity reporter installed. Any ideas to get it to work?

add-on compatibility reporter starts to fail here too :/

I use now https://addons.mozilla.org/en-US/firefox/addon/checkcompatibility/ instead ^^

I can reproduce this issue. Looking into fixing it now.

Edit: this is most likely due to the moz-border-image changes.

Edit2: This should work for the default curved tabs:

.tabbrowser-tab[selected="true"] .tab-stack {
  border-width: 0 28px !important;
  border-style: solid !important;
  -moz-border-image: url(chrome://browser/skin/tabbrowser/mrcurve.png) 0 28 fill !important;
}

The problem is I don't think I can have support for both Firefox stable/aurora and Nightly at this point because of the changes.

I can reproduce this issue. Looking into fixing it now.

Edit: this is most likely due to the moz-border-image changes.

Edit2: This should work for the default curved tabs:

.tabbrowser-tab[selected="true"] .tab-stack {
  border-width: 0 28px !important;
  border-style: solid !important;
  -moz-border-image: url(chrome://browser/skin/tabbrowser/mrcurve.png) 0 28 fill !important;
}

The problem is I don't think I can have support for both Firefox stable/aurora and Nightly at this point because of the changes.

Weird that I don't have it :/

Maybe because of UX build?

I can reproduce this issue. Looking into fixing it now.

Edit: this is most likely due to the moz-border-image changes.

Edit2: This should work for the default curved tabs:

.tabbrowser-tab[selected="true"] .tab-stack {
  border-width: 0 28px !important;
  border-style: solid !important;
  -moz-border-image: url(chrome://browser/skin/tabbrowser/mrcurve.png) 0 28 fill !important;
}

The problem is I don't think I can have support for both Firefox stable/aurora and Nightly at this point because of the changes.

Could you please update the Stylish "Classic tabs" theme?

How do I make this compatible with the latest Aurora build? I have the add-on compatibility reporter installed, but this stopped working in Aurora.

Use: https://addons.mozilla.org/en-US/firefox/addon/checkcompatibility/

UX builds use an older code base. When they are updated to use the mozilla-central code (Nightly) it should include that change.

I can confirm it's updated now and ux-builds are affected too ;)

Could you please update the Stylish "Classic tabs" theme?

This works for Classic tabs:

.tabbrowser-tab[selected="true"] .tab-stack {
margin: 0 -3px 0 !important;
padding: 0 2px 1px !important;
border-width: 0 9px !important;
border-style: solid !important;
-moz-border-image: url(chrome://browser/skin/tabbrowser/mrcurveless.png) 0 9 fill !important;
}[/CODE]

The problem is I don't think I can have support for both Firefox stable/aurora and Nightly at this point because of the changes.

Can't you just provide two sets of CSS code for the two Firefox versions, and link to both of them from the AMO page?

This works for Classic tabs:

.tabbrowser-tab[selected="true"] .tab-stack {
margin: 0 -3px 0 !important;
padding: 0 2px 1px !important;
border-width: 0 9px !important;
border-style: solid !important;
-moz-border-image: url(chrome://browser/skin/tabbrowser/mrcurveless.png) 0 9 fill !important;
}[/CODE]

Can't you just provide two sets of CSS code for the two Firefox versions, and link to both of them from the AMO page?

He can better use :after and :before instead of buggy border-image (which would work fine in all firefox since version 3) for the curve images :/

I have another method to do the tabs that will work with all Firefox versions.

Excellent! Thanks a lot for your work with this theme, it's the on thing I need to stick with Firefox and keep Chrome a distant memory.

On an unrelated note, do you by any chance know how to move the reload button in the address field to the left side? I tried to edit a Stylish script I found but to no avail as there was a large white space left, and I don't know how the Firefox UI works.

On an unrelated note, do you by any chance know how to move the reload button in the address field to the left side? I tried to edit a Stylish script I found but to no avail as there was a large white space left, and I don't know how the Firefox UI works.

Try this:

#urlbar-go-button,
#urlbar-stop-button,
#urlbar-reload-button {
  -moz-box-ordinal-group: 0 !important;
}

#unified-back-forward-button[disabled] + #urlbar-container &gt; #urlbar &gt; .urlbar-textbox-container {
  -moz-margin-start: 0 !important;
}

#unified-back-forward-button[disabled] + #urlbar-container &gt; #urlbar &gt; :-moz-any(#urlbar-go-button,#urlbar-stop-button,#urlbar-reload-button) {
  -moz-margin-start: -13px !important;
  position: relative !important;
}

#unified-back-forward-button[disabled] + #urlbar-container &gt; #urlbar {
  -moz-padding-start: 0 !important;
}

The tabs seem to be misaligned in the Options dialog:

These are rendered by Firefox, in the next release I'll include some custom styled ones.

I forgot to add, the Inspect Element UI is not using the recently implemented one, I don't know if this is by design.

Thanks for this amazing theme.

This is a weird bug. I've included the new stylesheets to style the bar, however it isn't being styled.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • For the purpose that it was built for, it’s a great machine. It’s okay to own multiple machines, it’s okay for machines to be different. If every computer was the same, they’d be boring af.
    • OpenAI is rolling out a major upgrade to ChatGPT memory by Pradeep Viswanathan OpenAI is rolling out a major upgrade to ChatGPT's memory, making the system more capable, current, and scalable across long-term use. Memory allows ChatGPT to remember useful details about users, including their preferences, projects, and constraints. Instead of starting every conversation from scratch, ChatGPT can use this context to provide more relevant responses in future chats. OpenAI first launched saved memories in February 2024. That feature allowed users to explicitly ask ChatGPT to save information into its memory, such as travel plans or writing preferences. However, this system had limits because it depended heavily on users giving clear instructions to remember something. Additionally, saved memories could become stale over time. In April 2025, OpenAI expanded memory by allowing ChatGPT to reference past chat context outside the saved memories list. This was powered by a background process called “dreaming,” which automatically curates memories from chat history. This made ChatGPT better at learning from natural conversation without requiring users to manually save every detail. Today, OpenAI announced a more capable and compute-efficient memory architecture built on top of dreaming. This new system improves ChatGPT’s ability to carry forward useful context, follow user preferences, and remain accurate as time passes. According to OpenAI’s internal evaluations, the new system improves factual recall from 67.9% in 2025 to 82.8% in 2026. Preference adherence improves from 55.3% to 71.3%, while accuracy over time improves from 52.2% to 75.1%. The best part of this new system is a new memory summary page where users can review ChatGPT's memories. Users can even update details, correct information, or give instructions on what topics ChatGPT should bring up and when. This new, improved memory system is available to ChatGPT Plus and Pro users in the US starting today. It will roll out to more countries, as well as Free and Go users, in the coming weeks.
    • I work for a video production company in Australia. The camera operators shoot footage and then pass the SD card over to the editors. Much easier than handing over the entire camera. Plus, on a busy day you can hand off the SD card and then pop another in for the next shoot. Or, you might have used multiple SD cards because you need the extra space for a long shoot. I also use USB cables and wifi for transferring footage, but in many cases an SD card reader is the easiest method.
  • Recent Achievements

    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
    • Very Popular
      s0nic69 earned a badge
      Very Popular
    • Collaborator
      Asgardi earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      472
    2. 2
      PsYcHoKiLLa
      247
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      67
    5. 5
      Michael Scrip
      59
  • Tell a friend

    Love Neowin? Tell a friend!