iFrame resizer with chrome 67 causes flickering - google-chrome

We have an iframe resizer in use with the default settings.
Until the upgrade to chrome 67 it worked fine.
When I am using chrome 67 on a macbook pro (13") every change in the view causes the screen to flicker.
When used on an external monitor it works fine, also works fine on firefox.
We couldn't find any known issue on chrome, but this is a pretty new version.

Just to close this issue if someone will encounter this in the future.
This is a bug in chrome.
We contacted the chromium team and they are on it.
You can follow the discussion here: https://bugs.chromium.org/p/chromium/issues/detail?id=852348

Related

Chrome Version 102.0.5005.63 (Official Build) (64-bit) invalidate session after 30 seconds

We are seeing a really weird issue with our production site where after 30 seconds it appears that the session is invalidated in the Chrome and Edge browsers. We don't see any errors in the chrome inspect console.
We saw this behavior on 25MAY2022 right around when chrome 102 got pushed to the browsers at 5pm. IF we use inspect and turn off the cache then we don't see any issues with loading the site and everything operates fine.
FireFox works fine.
I'm using chrome 101.0.4951.61 against the same site on my android 11 phone and I cannot reproduce the issue.
Are there any new features in 102 we could turn off to see if a specific new security check might be at play?
My team is experiencing a similar issue when calling our API. If you go to chrome://flags/#private-network-access-send-preflights, and disable it, does that resolve your issue? If it does, then adding this header to your site may resolve the issue:
Access-Control-Request-Private-Network: true
We are currently doing pre-prod testing which is so far promising.
https://developer.chrome.com/blog/private-network-access-preflight/
Chrome ERROR_TIMED_OUT in latest version

LocalStorage disappears in chrome after page refresh

It's fine on the first load but as soon as I refresh, despite it being available from the console, it's not visible in the applications tab.
What do I do about this?
I'm on version 57.0.2987.133
As wOxxOm mentioned, this is currently a bug on Chrome but fixed in canary 59. I'm on 58.0.3029.110 (64-bit) and still seeing the issue.
You can try on Safari and shouldn't see the issue.

UI5: No press event triggered after updating Chrome

For some unknown to me reason, I cannot select sap.m.IconTabFilter, like it's not pressable (on mouse hover pointer is not appearing and when I press, nothing happens). This issue is experienced in Chrome. In Mozilla it works fine.
When I copied the XML into JSBin in Chrome, it worked fine.
Did anybody stuck with the same problem? How to fix it?
I tried to clear cache, restart browser/pc - the issue persists.
Also, same issue I'm experiencing right now with sap.m.Switch control.
UPDATE: I think it's a PC-specific issue. The problem is that in Chrome the app decides it's running on a tablet (instead of a laptop. The laptop can work as tablet too, but I run the app in laptop mode). This applies corresponding app's behavior. Maybe this can be the root of the problem?
No custom CSS is applied, only default ones.
I assume you are using Chrome 55+ which comes with active PointerEvent and won't work with certain UI5 versions. You need to upgrade to 1.28.42, 1.38.14 or 1.42.8 or deactivate the feature in Chrome via:
chrome://flags/#enable-pointer-events
in the address bar.

KineticJS 4.6 no longer working in Chrome 29

I'm working on a project using KineticJS version 4.6 (currently the latest version), and since last night's Chrome update to Chrome 29, the Kinetic canvas is completely blank. While using the console, I am still able to detemine that the created objects, such as the Kinetic.Stage and Kinetic.Layer, still exist and are filled with correct data.
Afterwards, I tried loading the same page in Internet Explorer and Firefox, and they still work as intended, showing the canvas with the correct elements.
I have tried searching for people with similar issues, but I guess Chrome's update is too recent to show any results. Does anyone perhaps know if there is a way to fix it or if I should simply wait for either a KineticJS or a Chrome update?
EDIT: And now it suddenly works again after restarting Chrome. Hotfixed?
EDIT2: After a while it broke again, but restarting the browser seems to work
EDIT3: It is a bug in Chrome, acknowledged by the Chromium team in this thread. The thread states that the bug is definitely fixed in version 30, which is currently in beta. This fix may be merged in version 29 soon, but there is no definitive timetable for this.
We have the same problem in Chrome 29.
In some cases a workaround is to tell your users to use Chrome Incognito mode to fix this issue.
A test to replicate the issue consistently is posted here:
https://github.com/ericdrowell/KineticJS/issues/585
At present, the bug is not present in Chrome 30. (8/27/2013)
You should star this chromium issue:
https://code.google.com/p/chromium/issues/detail?id=280153

Text flow out of divs in chrome, but not on all chrome users?

I got a really strange problem, and after so much tries and research I can't get out of it.
I have a website, but SOME (just 5% of visitors) people with the SAME version of chrome, see the text flowing out of divs and text overlapping. It's very strange because I tested the website on all chrome browsers using browser testers, without any problem. And in internet explorer or firefox this problem never happens...
A page is located here
And here are some screenshots of what SOME people see (maybe you won't see this in chrome)
click here
Maybe it is because of the font face I am using? Or maybe some bad coded CSS?
Please help me out of this!
Thanks a lot!
I see you use .svg font. Recently I was hunting some Chrome font rendering bugs and saw this:
http://code.google.com/p/chromium/issues/detail?id=95102
This seem very similar to issues you are having. You could try to serve some other font type to Chrome and if this would fix that.
If you don't want or can't serve some other font type to Chrome, the only thing you can do is wait until Chrome version 24 is out to all users which should be soon (I can't find any announcement)
I tested it in
Chrome 23.0.1271.97 m
Chrome 26.0.1371.0 canary
Chromium 25.0.1334.0 (169326)
# Windows 7 x64 and your page seems fine for me.