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

    • I think the car analogy is more this: Left hand drive, basic commands on the left side of the infotainment screen. Right hand drive, basic commands on the right side of the infotainment screen. Granted, you're not swapping between the two often so it's doesn't really work. But it's to do with the proximity of you (your mouse, or the driver) to the controls.
    • I mean, the old one was broken and so stupidly complex for many users, so I don't see that as a feasible option. A context menu needs to be simple to use, and for me the Windows 11 style actually worked really well for me, and many others. I used to have to scroll the damn context menu just to get to "file properties" in Windows 10. That was not a good experience, and I'm sure you'd agree. What they're trying to do is make it the best of both worlds, as clearly you'd prefer the Win10 style. I'm curious how they're going to do this.
    • The "Show more options" has its place, as does the simpler context menu, but it should perhaps be a separate fly-out rather than relaunching the entire, old context menu. The old context menu was getting absurd in Windows 10. Often I'd have to make the context menu scroll just to get to "File properties" on my old laptop. Even without much installed, the amount of items was just too much. It's a context menu, not a "do all" menu. Making it configurable is fraught with challenges too, so I'm interested to see how Microsoft tackles this one.
    • I don't hate the new menus, I am not a fan of the lack of features and how they went live when they clearly are not complete. The menu itself presents much better than the previous - but what's lacking (IMO) is: 1) Any kind of automated manipulation such as: "this goes on the new menu because you use this feature more often on this filetype" "this is rarely used and will fall back to the old menu" 2) Any kind of user manipulation such as: "a UI to add/remove/order items to the new menu"
  • Recent Achievements

    • Week One Done
      I2D earned a badge
      Week One Done
    • 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
  • Popular Contributors

    1. 1
      +primortal
      484
    2. 2
      PsYcHoKiLLa
      262
    3. 3
      Skyfrog
      86
    4. 4
      FloatingFatMan
      64
    5. 5
      Michael Scrip
      63
  • Tell a friend

    Love Neowin? Tell a friend!