Támogatás keresése

Kerülje el a támogatási csalásokat. Sosem kérjük arra, hogy hívjon fel egy telefonszámot vagy osszon meg személyes információkat. Jelentse a gyanús tevékenységeket a „Visszaélés bejelentése” lehetőséggel.

További tudnivalók

A témacsoportot lezárták és archiválták. Tegyen fel új kérdést, ha segítségre van szüksége.

New Update 29 = Tabs not able to move bottom anymore. :(

  • 22 válasz
  • 175 embernek van ilyen problémája
  • 17 megtekintés
  • Utolsó üzenet ettől: Yozilla

more options

Tabs in new update 29 do not move to bottom anymore, So I uninstalled 29 Went here http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/28.0b9/ downloaded the 32 win one and rerolled back to version 28, everything back to normal :). I'll wait till this is fixed in the about:config if ever or there is a fix that isn't too complicated. otherwise I may even move on. I have been a dedicated firefox user since netscape.

Tabs in new update 29 do not move to bottom anymore, So I uninstalled 29 Went here http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/28.0b9/ downloaded the 32 win one and rerolled back to version 28, everything back to normal :). I'll wait till this is fixed in the about:config if ever or there is a fix that isn't too complicated. otherwise I may even move on. I have been a dedicated firefox user since netscape.

Kiválasztott megoldás

Hi thanks yes it worked, but, why should I have had to add an addon? why is it firefox mozilla devs are getting rid of what we like and have preference for? I'm very aware of addons, My anger is based on there stupidity to get rid of stuff, which could and probably has got rid of some dedicated firefox users. I'm using the addon but I still would prefer if Firefox devs made some thoughful decisions when taking things away during updates. Thanks

Válasz olvasása eredeti szövegkörnyezetben 👍 11

Összes válasz (2)

more options

So, this isn't happening when you disable the userChrome.css file by renaming the file to userChrome.css.sav?

Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem.

  • Switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance
  • Do NOT click the Reset button on the Safe Mode start window

In Firefox Safe mode these changes are effective:

  • all extensions are disabled (about:addons)
  • default theme is used (no persona)
  • userChrome.css and userContent.css are ignored (chrome folder)
  • default toolbar layout is used (localstore-safe.rdf file)
  • JavaScript JIT compilers are disabled (prefs: javascript.options.*jit)
  • hardware acceleration is disabled (Options > Advanced > General)
  • plugins are not affected
  • preferences are not affected
more options

If I delete or rename the userChrome.css file the tabs are back on top and the jitters are gone. When I reinstate the file with the correct name the jitters return. Visually, it looks like the tabs (on the bottom), the bookmark toolbar and the main toolbar seem to compress into the title bar. The title bar is static and doesn't change when this happens. The most notable thing is that the icons (but not the text) for the sites I have on the bookmark toolbar (26 items on the bookmark toolbar for several years now) are what disappear and are rewritten. The jitter effect also occurs when I print from Firefox, though I should add that 99% of the time I print from Firefox (for the last several years) I print to CutePDF. The bookmark icons don't disappear when I print; they just compress a bit. Despite that, i seriously doubt CutePDF has anything to do with it since it never happened before two days ago when I modified the userChrome.css file.

And as I said before, it's no big deal for now. Tabs on the bottom are the higher priority for me now. But if that changes I still have the options I mentioned in my previous post. If it helps, I'm using a Dell Inspiron with Windows XP, SP2. Screen resolution is set to 1440 X 900, 4 Gigabytes of memory and plenty of room on the hard drive. It is definitely related to the userChrome.css file, and though I doubt it, I suppose there is a small chance it could have something to do with the hardware.

Módosította: Yozilla,

  1. 1
  2. 2