What i dont want is that scroll which is coming over fixed navbar.
This is fine in windows, macbookpro 2011 with el capitan and macbook mini. But I see this issue in macbookpro 2011 with yosemite and macbook air with el capitan.
On all of these devices i'm using the latest google chrome browser Version 47.0.2526.106 (64-bit).
Please refer to these screenshots jsfiddle screenshot
and here's the example jsfiddle link
This is the code enter code here
Any help would be greatly appreciated.
this css property -webkit-transform: translate3d(0, 0, 0) worked for me.
Thanks to #jackysee
Related
I am hoping that someone could help me with this, I've been trying to figure it out why the other tabs are missing. It started after I updated my Safari version to Version 14.1.1 (15611.2.7.1.6, 15611).
OS: Mac Pro MacOs Catalina - 10.15.7 (19H1217)
Browser: Safari Version 14.1.1 (15611.2.7.1.6, 15611)
I wonder if there are settings that need to be configured?
While working OpenGL code using SDL 1.2 and 2.0 on MAC Mojave, the SDL window is now showing a black screen (It was working perfectly before updating to MACOS Mojave).
I googled a solution for a while and I didn't find any.
The only thing that solved the issue was updating to Mojave 10.14.3 and Xcode 10.1 . I recommend you to do the same
Downgrading is not treating the problem, it's just masking the symptoms.
the SDL window is now showing a black screen
To me this looks like an issue with double buffer configuration and/or use. But it's hard to tell without seeing some code.
I am doing cross browser testing in browser stack. My protractor tests are passing on all other browsers: Chrome, IE-11, Edge, Firefox but few tests are failing on Safari 9.1 on mac El Capitan. When i used the High Siera and Saffari 11, it will click on the link that was not cliked earlier on safari 9.1 and El Capitan but other tests that were passing on Safari 9.1 and El Capitan were failed. So i am tried with doiing back and forth and unable to make all the test script pass. I am using repeater locator to find the element. Can someone help me to resolve this issue or help me how to deal with this situation.
Thanks in advance.
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});
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.