Using http://lab.hakim.se/reveal-js/#/ and found (even with this site) Edge Browser (Windows 10) is not showing some content (some animated text appears during transitions and then disappears.
I have similar behaviour (test example):
http://restacres.com/portfolio/#
Edge has menu option to show in IE... which works.
As of the date of this posting I ensured my Windows Updates were at the latest.
Please compare in Edge vs other Browsers. I have it working as expected in Chrome, IE 11, Safari, including on numerous phone Browsers (Z10, iphone).
Any suggestions (other than waiting for more updates). Any one else seeing similar behaviour?
Thanks,
Craig
Related
I have a front-end component for a project that's exhibiting the following bug:
There's a button at the bottom of the screen of one of my Panes and ONLY on chrome on iOS does the button not show. If I tap the address bar, then the button appears presumably because the pane has redrawn itself.
The other problem is that I can't recreate the bug. It only appears on a client's web app. Things that could be super helpful:
what's a good way to inspect Chrome on iOS? (I know how to inspect Safari on iOS, Chrome on Android, but not Chrome on iOS. I've also already tried the devtools mobile emulator and it does not reproduce there)
any related posts for bugs on Chrome on iOS (I've done some search already but if anyone has something deep in the internet that they remember)
any knowledge of how Chrome renders things differently than Safari for iPhones
any ideas on intermediate solutions
any ideas on potential causes
Exactly as the title says: my code expands a SafeFrame to fill the window when clicked, using $sf.ext.expand($sf.ext.geom().exp);. The base ad-unit renders without issue, but the attempt to expand fails every time.
This works fine in Chrome, Firefox and Safari, on desktop and mobile, and was working in Edge version 40 - but not the latest version (41.16299.15.0).
The issue seems to be limited to Google's SafeFrame implementation.
The tester at http://safeframes.net/examples/creative_test.html (which, as far as I can tell, uses the IAB reference implementation) works just fine in every browser I can find...
...whereas http://publisherconsole.appspot.com/safeframe/creative-preview.html, which uses GPT, exhibits the same behaviour (works everywhere but Edge 41).
Has anyone found a workaround for this?
UPDATE: As of 2018-02-22, GPT SafeFrames expand correctly in Edge 41, as everywhere else. As there hasn't been an Edge update, Google have presumably silently fixed the issue on their end.
There is a JQuery custom scrollbar on the page http://baijs.nl/tinyscrollbar/ and when viewed with either Opera or Mozilla the scroll works just nicely, but when viewed with Safari or Chrome, there is this annoying lag/latency (about 1 second) from dragging to reaction, that should be seemless.
I'm using Windows 7 Pro x64.
Found something, that may be related:
Very slow JavaScript performance using tinyscrollbar update
I'm pretty new to web-coding and in my attempt to create jQuery based menu bars complete with dropdowns I have stumbled upon some vast differences between broswers. Below you can see that while FF and Safari are the same, IE is actually behaving and Opera is ok-ish, Chrome gets it totally wrong. As far as I can tell I have all the latest versions.
I removed the code from here and pasted it in: (doesn't want to let me link properly) so: jsfiddle.net/2hCR2/
Just in case, support for older versions of IE (6-7) is not required.
Right now I'm mostly concerned with the positioning aspect. Any assistance is much appreciated!
****EDIT:** After continuing to play with the chrome developer tools I realized that when I manually set the 1st list (pants/t-shirt) to display:block it displays as expected (exactly like FF and Safari in the image) so it appears that this is more of a javascript/jQuery issue not updating the DOM correctly(?). I also noticed that when I put the code is JSFiddle and ran the script in Chrome it produced the same error, but when I ran JSFiddle in FF (exact same fiddle link) it renders correctly.
It does not happen in Chrome Canary (version 24) but it does in stable (version 22). Apparently it is a bug which has been fixed.
You can either wait a month or two so that all Chrome users get the fix, or just use .show() instead of .show(0).
I'm testing jquery-mobile with Opera Mobile browser. There are bugs, which are visible on both Opera Mobile Emulator and Opera Mobile on mobile device. On both they are occuring randomly (often, but not always).
The most visible is with refreshing list with listview('refresh'); call. Sometimes the changes are not visible, and the pure HTML before the modifications is displayed. But after tapping the device the changes became visible.
And also, some clicks on buttons does not work. Most of the time it works, but sometimes the button need to be pressed a few times.
JQuery version is 1.6.4, jquery-mobile version is 1.0.
Did you find similar bugs, or know what is causing them and how to prevent them? I think that jQuery-mobile is using some unstandard behaviour, which is working on other browsers, but is causing bug under Opera, because most of the apps works fine, but some are causing problems only under Opera/Opera Mobile.