Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

starting from 85.0 firefox no longer switches to a previously opened tab

  • 4 wotmołwy
  • 1 ma tutón problem
  • 10 napohladow
  • Poslednja wotmołwa wot edward.shevtsov

more options

Hello,

I am using firefox to develop websites in wordpress. The WordPress editor has the ability to preview the edited page in a new tab.

Pre-85.0 standard behavior: 1. The edited page opens in a new tab (for the first time). 2. Firefox switches to this tab, making it active 3. For all subsequent development iterations, the firefox updates the contents of this tab and switches to it, making it active.

In version 85.0: 1. The same 2. The same 3. Firefox updates the contents of this tab, but DOES NOT switch to it. This tab remains passive

Any ideas? Thanks

Hello, I am using firefox to develop websites in wordpress. The WordPress editor has the ability to preview the edited page in a new tab. Pre-85.0 standard behavior: 1. The edited page opens in a new tab (for the first time). 2. Firefox switches to this tab, making it active 3. For all subsequent development iterations, the firefox updates the contents of this tab and switches to it, making it active. In version 85.0: 1. The same 2. The same 3. Firefox updates the contents of this tab, but DOES NOT switch to it. This tab remains passive Any ideas? Thanks

Wšě wotmołwy (4)

more options

I don't use preview enough to remember how it behaved before, but I see what you mean. Even though the script that updates the preview tab has this function call, which I assume is meant to switch tabs, it doesn't seem to work:

this.previewWindow.focus()

Firefox has a preference that generally prevents sites from changing the order of windows, for example, putting a popup in front of everything. If I disable that protection, then WordPress switches tabs. I don't know why it worked with this protection before but not now. If you want to try disabling that as a workaround while you're editing, here's how:

(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button accepting the risk.

(2) In the search box in the page, type or paste flip and pause while the list is filtered

(3) Double-click the dom.disable_window_flip preference to switch the value from true to false -- to change it back, you can just double-click again

If you wanted to get more to the bottom of this, and you have a free hours, you could run Mozregression, a tool to pinpoint the change that broke it. However, it would be helpful to have a much simpler way to test than having to keep logging into your admin area and editing a post.

https://mozilla.github.io/mozregression/

more options

I filed a bug. Hopefully it will get fixed by Firefox 86 next month.

more options

Looks like this will get fixed in Firefox 86, expected to release on Feb. 23.

more options

Thank you very much for your support!