My dev Firefox is basically just an Ubuntu Firefox run from an LXC container, it might also be the Firefox Developer edition, or Ive just installed the additional debugging extensions that normally come with that. This is an interop-driven change, to align Chromium with the newly-landed spec for window.open. New popup window appears blank until right-click. Eventually it has to be started by the client so either with a button click or in another example i had GridView click opening the popup. I solved that problem by putting the Javascript in a OnClientClick event. Now, those all return true if you got a new window/tab, and false if you got a popup. It may be the same thing I have in Firefox and Chrome, the popup (window.open) is blocked. ) which didn't correctly represent what was actually visible.
This change simplifies the usage by adding a single boolean argument called 'popup' that works as you'd expect: popup=1 gets you a popup, and popup=0 gets a tab/window:Ĭonst popup = window.open('_blank','','popup=1') Ĭonst tab = window.open('_blank','','popup=0') Īlso there were previously confusingly-behaved getters for the BarProp visible properties (e.g. The window.open() API is currently confusing to use, in terms of trying to get it to open a popup vs. When I entered 2 it opened up links in a new window so I entered 1 and that.
#Firefox popups new window how to
tab/window, and 2) ensuring all BarProp properties return !is_popup. How to make firefox open popups in new tab or stop from opening in new tab. This change aligns Chromium with the spec for window.open(), by 1) adding a "popup" windowFeature to control popup vs.
0 kommentar(er)
