Hello,
Here's the list of new issues found and filed by the Desktop Release QA
team in the last 7 days.
Additional details on the team's priorities last week, as well as the
plans for the current week are available at: https://tinyurl.com/yxa63vns.
Bugs logged by Desktop Release QA in the last
On 9/8/19 8:28 AM, Andreas Tolfsen wrote:
It would be fine of course to move the existing behaviour to
chrome-only mozOuterWidth/mozOuterHeight
For what it's worth, out current outerWidth/outerHeight getters already
check who the caller is and don't apply the Tor bits if the caller is
system
Also sprach David Teller:
> Have you checked that we don't use it internally in Firefox to e.g.
> position tooltip menus? If so, we may need workarounds for the UI
> and possibly WebExtensions.
Indeed, we rely on these properties extensively in both frontend
and automation.
It would be fine of c
Have you checked that we don't use it internally in Firefox to e.g.
position tooltip menus? If so, we may need workarounds for the UI and
possibly WebExtensions.
Cheers,
David
On 08/09/2019 06:57, Tom Ritter wrote:
> Summary:
> window.outerHeight/outerWidth are legacy properties that report the
window.resizeTo() should also use innerHeight/innerWidth instead of
outerHeight/outerWidth. Otherwise web pages can open a popup, call
window.resizeTo(), and get innerHeight/innerWidth to circumvent the
restriction.
On 2019/09/08 13:57, Tom Ritter wrote:
> Summary:
> window.outerHeight/outerWidth
5 matches
Mail list logo
