Status Update
Comments
al...@gmail.com <al...@gmail.com> #2
Information redacted by Android Beta Feedback.
al...@gmail.com <al...@gmail.com> #3
Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
sa...@google.com <sa...@google.com> #4
fa...@thexs.ca <fa...@thexs.ca> #5
Thank you for reporting this issue. We have a fix rolling out in an upcoming release.
jo...@johannesklampfl.com <jo...@johannesklampfl.com> #6
ml...@spplus.com <ml...@spplus.com> #7
fa...@thexs.ca <fa...@thexs.ca> #8
Updating the original post/comment #1 above, after some more tests
Chrome latest update makes the add-on sidebar/dialog gone blank (whiteout) when switching through several tabs
After the Chrome update to version 87.0.4280.66 the add-on UI, either a sidebar or a dialog is going blank (whiteout) after the browser tab where the add-on is showing gets to the background, among several other tabs
This is happening
- in Ubuntu Linux and in Windows, I haven't tested on iOS so far
- and at least for Google Sheets and Docs add-ons, I haven't tested on Slides and Forms so far
After several tests, this is happening consistently in the following scenario
- Open a new browser window
- Open a Google Spreadsheet (or Docs, etc)
- Open any add-on sidebar (or dialog)
- In this case the Mapping Sheets add-on sidebar
- Open a new tab with some content
- Select tabs one by one from right to left
- Repeat the two previous steps until getting a blank sidebar issue
- You might need from one to several extra tabs to reproduce this issue
Funny though (not really),
- While being in blank, the content is still there because on mouse over you can find and click links and buttons there
- And if you resize the window or sidebar height, the content shows there again (not an option for a dialog)
Please, check these two short videos (~20 secs) showing this Chrome/Add-ons issue in action
- On a Ubuntu Linux device, where it happens with just (1) one extra tab
--
https://youtu.be/l3gE77DaC6A - On a Windows 10 device, where it needs several (5) extra tabs to happen
--
https://youtu.be/yICbUgpsMTw
In my view this is a serious problem, that potentially could affect millions of users across the many Google Editor add-ons out there
- Mostly because it comes from a historic performance improvement update in Google Chrome, that is making Google Editors add-ons vulnerable
- The add-on user interface runs inside a triple-iframe that seems to be "whiteout/forgotten" when that browser tab stays in the background queue long or deep enough
Thanks in advance for your prompt attention to this matter
sa...@google.com <sa...@google.com> #9
I understand that you experiencing this behavior, however I do not have any direct connection to Google Chrome and if I were to report to the issue to Google Chrome - it would not be any different than any other user reporting it, the Chrome issue reporter uses a different platform, so there is no such a thing as "internal communication" between Google Apps Script and Google Chrome. So I would need to ask you to contact Google Chrome yourself.
Thanks for your understanding.
aj...@gmail.com <aj...@gmail.com> #10
m....@gmail.com <m....@gmail.com> #11
Tested and replicated in Version 87.0.4280.66 (Official Build) (64-bit) Win 10
Tested not replicated in Version 88.0.4324.11 (Official Build) dev (64-bit) Win 10
I understand this is a different product team but rather than waiting for the Chrome team to push 88.x could the Google Apps Script team not push a patch for add-on behaviour. Not tested myself but would nudging a resize on a visibility change state force the iframe to render (see attached)
pe...@amplifiedit.cdw.com <pe...@amplifiedit.cdw.com> #12
pe...@amplifiedit.cdw.com <pe...@amplifiedit.cdw.com> #13
fr...@gmail.com <fr...@gmail.com> #14
Affected as well. @pe...@amplifiedit.com, are you sure it's the same issue? Looks like the Chromium issue is relative to text being blurry inside an iframe. Not the iframe content being blank after some inactivity.
Does anyone has reported this issue to Chromium team?
fr...@gmail.com <fr...@gmail.com> #15
I've reported this issue here:
Unfortunately, I haven't been able to reproduce this issue outside of Google Workspace add-ons. Dear Google, could you have a second look at it? Might be your nested iframes configurations that are doing something wrong. Thanks!
mi...@jivrus.com <mi...@jivrus.com> #16
This is impacting all our add-ons, especially those requiring OAuth authentication to connect with external applications. After it connects with the external application on a new window, when our users come back to the add-on it becomes blank.
It requires a fix either in Chrome or in Apps Script Sidebar rendering - both in the hands of Google.
Appreciate it if you could fix it before more people start disliking it.
fa...@thexs.ca <fa...@thexs.ca> #17
I did report the issue to Google Chrome, on Nov.24 early morning (EST), I sent them the whole
I guess that what it said about gsuite in
Either, we will soon find out, because the patch has been approved to merge with version 87
fr...@gmail.com <fr...@gmail.com> #18
Thanks @fa...@thexs.ca - I've updated my bug report to Chromium Team.
Dear Google, I really suspect this is going to turn really bad as more and more users have their Chrome auto-updated. All add-ons are impacted on Google Workspace.
fr...@gmail.com <fr...@gmail.com> #19
Reproducible example:
ho...@gmail.com <ho...@gmail.com> #20
I'm experiencing white iframes but am not changing tabs though. This started to happen as the latest Google Chrome update was installed.
fa...@thexs.ca <fa...@thexs.ca> #21
It looks like the issue was fixed with Chrome version 87.0.4280.88
Description
After today Chrome update to version 87.0.4280.66 the add-on UI, either a sidebar or a dialog is going blank after the browser tab where the add-on is showing gets to the background
This is happening in Ubuntu Linux and in Windows, I haven't tested on iOS so far
Not sure if I am explaining this in the right way, neither I have found all the possible combinations to reproduce the issue
But it's happening consistently in the following scenario
Funny though,
There are other scenarios as well, but this is the most clear for me so far
Is somebody around having the same issue with the latest Chrome version?
Thanks for your feedback either way
Fausto