I upgraded to Mountain Lion yesterday, which includes Safari 6.
Unfortunately, it have some weird -webkit-transform bugs?
Check this url:
http://dropshado.ws/post/1301087289/webkit-transform-perspective-function
Safari 6 shows this (nothing at all...):
And Chrome shows this (the right way):
Does anyone have these problems too?
Was having this problem on my company's website and figured out with my co-worker that adding overflow: hidden to the container div seems to fix the issue in Safari 6 on mountain lion.
Works on our site and your example. Strange!
I've been having the same problems with any rotations about the X or Y axis in Safari 6 (running Mountain Lion). The latest webkit build doesn't seem to have any problems, so this must be a bug.
The odd thing is that if you select the element that should have had a transform applied from the DOM tree in the Web Inspector, it highlights the element as if the correct transform has been applied.
Many examples around the web still render correctly in Safari 6, so perhaps there is more to this than meets the eye.
Related
I can't see many icon when I use Safari (but I don't have this problem when using Chrome)
I initially imagined my MacOS had lost its fonts and had problems but I tried reinstalling the machine several times and the problem was still not resolved (but when MacOS is on MacOS Catalina, Safari doesn't have this problem)
Is there my MacOS has a problem or the safari does????
I try to fix it many day and so tired
I can’t see any icon in the font awesome web and another website
Have a look at the attached image
the Safari browser with macOS High Sierra Version 10.13.
Also there is a video
https://share.vidyard.com/watch/AZyZGJJ4tJvAQDCYiUQD6W with a closed issue. It is this plugin http://3dflipbook.net . Generally the plugin works well. This problem was not met on other OS: Windows, Android or iOS. Does anyone has any ideas what is wrong?
Best regards,
Ivan.
[1]:
I'm also experiencing this bug, only happens in safari on high sierra. Have you logged an issue with WebKit? I was about to do the same thing.
Can confirm that WebGL in Chrome is broken in Mac OSX High Sierra. I'm on a 2011 MacBook Pro.
Same machine, Firefox Quantum can play WebGL however
Testing using https://get.webgl.org
Most odd
This bug happens because we disabled anti aliasing for the webgl context. If you turn it back on the issue goes away. Probably not the answer you want if like us you're doing it in the shaders instead. The guys from webkit have already fixed the issue their end and its fixed in the latest technical preview of safari so just waiting for it to get to the release build
One of my customers confirmed, using antialiasing resolves the issue. So create render in this way:
var renderer = new THREE.WebGLRenderer({ antialias: true});
Since upgrading to Sierra, clicking any text within PhpStorm 2016.2.1 results in a random block of text being selected and clicking within that moves the text around randomly instead of deselecting the text block.
Worked without a problem in El Capitan.
This has made PhpStorm into an extremely frustrating and productivity killing experience.
Any idea how to fix this?
Please see the latest EAP build here (I haven't yet tried it myself): https://blog.jetbrains.com/phpstorm/2016/10/phpstorm-2016-3-eap-163-5644/
Issue is tracked as https://youtrack.jetbrains.com/issue/IDEA-161617. Please check if the problem persists in the custom JDK build: https://youtrack.jetbrains.com/issue/IDEA-161617#comment=27-1642308
I found that turning off the "three finger drag" feature dramatically reduced this issue.
Follow the instructions in Apple's support docs for this.
It seems that under Sierra the Magic Mouse has become so sensitive that even touching the edge of the mouse with my other fingers can be misinterpreted as a three finger drag attempt.
Still happens intermittently, so I'm hoping some update to the driver by Apple or the PHPStorm JDK will get rid of any lingering occurrences. For now, this is the best solution I've found thus far.
I just recently downloaded the latest public release of Xcode (6.3) and I noticed the storyboard for my app is now low res on my Retina MacBook Pro. Images, text and standard UI elements all appear blurry. On the actual device everything looks fine and code still looks sharp its just while working in the Interface Builder.
Has anybody else noticed this and figured out a way to fix it? This is happening to me in both Swift and Objective-C projects including in Apple's sample projects (Master-Detail Application and etc).
I submitted this as a bug report, and Apple responded by saying that it is the desired appearance. They did not give an explanation, that was all they said.
It appears to be related to a bug in the newest iOS SDK, and as a workaround, they've forced Interface Builder to render everything at 1x. Currently, there doesn't seem to be any solution to this annoying problem other than to wait.
Just installed Xcode version 6.3.2 and this issue appears to have been fixed.
Have you tried re-installation of the same version? That helped once.
Alternatively, can upgrade to newer version, too.
I started making a finance program yesterday. I didn't have internet, so I waited to search the problem up. I could not find anything that worked. I am using an NSTabView, and there are three tabs: income, assets, and net worth. Inside income, I have two NSTableViews. Inside assets, I have one NSTableView. The Clip Views in these three NSTableViews are not displaying. I have the newest version of Xcode (6.1.1), and am using Yosemite. There are also warnings that look like the following:
So if anyone knows about what might be happening or how to fix it, it would great if you could leave a comment or answer!
I believe this is a bug for XCode 6.1 on 10.10. When running on 10.9, there is no such warning.
Here is a similar question: Permanent Misplaced View warning for Clip View in NSTableView
I will Update this answer once I find a new solution other than downgrading my OS to 10.9.
Update:
I believe it is a bug of Xcode. And I do find a workaround to fix it(other than downgrading my OS to 10.9).
The solution is to edit the attributes of tableView in IB, disable "Headers". Don't show table headers and the warning will be magically gone. And we can guess that by default the table header is 17px :)
It's just a workaround, not an ideal solution. This is not our fault. The best solution is to wait for Apple to fix this Xcode bug.