We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

Cannot move Title Page using Noia 3.0.9 theme with OS X Lion; default theme is fine with FF 35

  • 5 отговора
  • 2 имат този проблем
  • 2 изгледи
  • Последен отговор от cvandray

more options

I have disabled all extensions and plugins and tested both themes and only the default theme works, with or without extensions and plugins. Short of refreshing Firefox, any other ideas out there?

I have disabled all extensions and plugins and tested both themes and only the default theme works, with or without extensions and plugins. Short of refreshing Firefox, any other ideas out there?

Избрано решение

My issue is now resolved with the FF 35.0.1 update. Thank you.

Прочетете този отговор в контекста 👍 0

Всички отговори (5)

more options

I have refreshed Firefox and no change in behavior. I will pursue with Noia developer.

more options

What title page? To where are you trying to move it? If you mean the title bar, I have never seen it anywhere but at the top of the window.

more options

Thank you finitarry for your interest in my situation. Please let me clarify: It is the Title Bar on the top of the window; with the defaut theme, I can move the Title Bar and all of the Tabs that show and thus, the window, to my secondary display and back should I chose to do so.

With Noia 3.0.9 as the active Theme, the Title bar remains fixed in its location and I cannot move it; I believe that this behavior was not present with FF 34 and I find this rather puzzling.

Thanks for your insight.

more options

I cannot help, since I have never used more than one display with a computer.

more options

Избрано решение

My issue is now resolved with the FF 35.0.1 update. Thank you.