#Enable javascript in firefox for mac mac osx#
"This issue will be fixed when Mac OSX 10.13 is released." We need to drop/replace the following sentence: Thanks for putting this together! A few comments:ġ. > Can someone check it to make sure it's right before we publish it? > OWvKqBC9YVJq4rqayo3qrJjRSvMjLdvXE7c/edit?usp=sharing (In reply to Joni Savage ("need info" me) from comment #50) At a minimum, we would lose the ability to interact with content/applications on other screens. At worst, we could open the door to crashes and other bad behavior.Ģ. rectangle defining the portion of the screen in which it is currently safe to draw your application content." It is hard to predict what could happen if we started drawing in a portion of the screen that is not considered safe to draw in. This is bad because it goes directly against what Apple says is the ". Ignore the values returned by visibleFrame].origin.y and visibleFrame].height and adjust it such that origin.y is always 0 and height is adjusted to cover the entire screen. A fix from Apple would address it across the board.ġ. I don't like either one of them and it would not address the fact that all previous versions of Firefox are affected by this. But on the other hand, going until Apple fixes this in 10.13.1 or mid November for 57 is going to be a long time where people are wondering why Firefox doesn't work with Youtube in fullscreen but Chrome does. It looks like 56 is scheduled for a few days after the release of High Sierra, so I guess either way this issue will still be present on High Sierra launch. How are they handling this scenario differently so that they're not affected? The main thing I have to say to this is, this issue doesn't existing in Chrome, Brave, and Safari. > workaround, we can still take an uplift to mozilla-release up till the > that to spohl and maybe mstange to figure out. > It doesn't sound like there is an easy or safe workaround, but I'll leave > well until Apple is able to fix the issue on their side. > I don't think we should block 56 on this issue it will be broken in 55 as
(In reply to Liz Henry (:lizzard) (needinfo? me) from comment #26) When the Dock is hidden, the visibleFrame's origin is and the visibleFrame's height is 80 less than the expected maximum screen height. Click the button, observe the console output. Compile and run the attached reduced test case.Ģ. The screen only extends up to the dock and the dock area is visible.ġ. The firefox window does not completely go fullscreen on macOS 10.13. The firefox window should completely go fullscreen. There are two options to reproduce the issue:Ī) Open the url ( ) in Firefox ESR 52.3.0 in Mac 10.13 beta 5 This is believed to be a bug in 10.13 because the Apple Developer Documentation neither mentions changes to nor visibleFrame].
rectangle defining the portion of the screen in which it is currently safe to draw your application content.", resulting in fullscreen mode to only extend down to where the Dock would usually appear, exposing the Desktop. This causes fullscreen issues in Firefox because the OS reports an incorrect ". This also impacts the visibleFrame's height, as it will be 80 smaller than expected. It used to be set to 0 on 10.12 and below. Specifically, if the Dock has a height of 80, visibleFrame].origin.y remains at 80 when the Dock is hidden. On macOS 10.13 Beta (17A360a), when the dock and menu is hidden via, visibleFrame].origin.y is not adjusted to account for the fact that the Dock was hidden.
MacOS 10.13 reports incorrect visibleFrame].origin.y and height when dock is hidden Here is what was posted in the radar bug: Details This appears to be a bug in macOS 10.13.
0 kommentar(er)
