Hangouts window not fully rendering (in gmail), empty frame opens |
||||||||||||||||
Issue descriptionVersion 53.0.2785.87 beta (64-bit) Platform 8530.77.0 (Official Build) beta-channel samus ARC Version 3233856 Firmware Google_Samus.6300.174.0 What steps will reproduce the problem? (1) have hangouts open in gmail (2) have multiple windows docked in gmail (chats, email draft, tasks) - I have seen this when I have at least 3 windows open (3) search for a contact in hangouts, click contact to open a new hangout What is the expected output? New hangout window opens and is usable What do you see instead? Main body of the chat window is not visible, can see the frame of the window and the controls are functional if happen to locate them and click Feedback reports: http://feedback.corp.google.com/#/Report/13186209537 http://feedback.corp.google.com/#/Report/20382692556
,
Sep 16 2016
@abodenha - can someone take a look? Seeing this again. https://screenshot.googleplex.com/rYbiXHpDqBV I have to scroll around to blindly find the x to close the empty frame, close an open window, and reopen. Version 53.0.2785.103 beta (64-bit) Platform 8530.81.0 (Official Build)
,
Sep 16 2016
Could this be the same as bug 637449 ? Is this happening mainly on samus with an external display connected?
,
Sep 16 2016
Adding a few others who might have insight.
,
Sep 16 2016
No external display. I've seen it on Samus and Cave but as per c#2 it maybe across devices.
,
Sep 16 2016
I have seen this happening on Chrome Mac OS X too. Please let me know if there is any Chrome side logs/feedback I can provide.
,
Sep 19 2016
Re Comment 3, bug 637449 only applies to Windows.
,
Sep 19 2016
robliao@ yep. The symptoms sounded similar enough that I wanted to double check that we didn't have a single root cause. Based on comment 6 I'm flagging this for Mac as well.
,
Sep 20 2016
,
Sep 20 2016
After discussion with Patrick Wong on the Hangouts team, the repro and screenshots suggest that this is a blink issue, especially given that all of the frames in question appear to be DOM elements. The UI in question is all in frame. For the record, I'm not able to repro this on Windows Canary or CrOS Beta.
,
Sep 20 2016
Right clicking the chat and selecting 'reload frame' makes it go transparent 100% of the time. However Sage from the Hangouts team said this is known, and unrelated.
,
Sep 20 2016
Right. The mechanism that hangouts uses to render the UI is that we load up a browser cached page in the frame, hand off a reference to the frame window to the main hangouts context, and the main hangouts context injects the dom. As a result rightclick refresh breaks the hangouts UI regardless of this bug.
,
Sep 26 2016
ping?
,
Sep 26 2016
We really need a repro for this. There are reports from users that they also see this issue in Safari (https://productforums.google.com/forum/#!topic/hangouts/42hqx0TM4HQ) and Firefox (https://productforums.google.com/forum/#!topic/hangouts/Ea78hX_D2nA).
,
Sep 27 2016
(oops, I did not mean to assign to Blink>Loader, I was trying to figure out where to assign it though) Also, more reports from Safari (https://m.reddit.com/r/osx/comments/4ftibf/gmail_chat_suddenly_not_working_in_safari/)
,
Sep 27 2016
I used to see this a lot, so much that I turned off chat in Gmail. I've turned it back on to try and repro this, but haven't seen it yet in 55.0.2868.3 (Official Build) dev (64-bit) on Mac.
,
Sep 27 2016
Also - the Hangouts team have said they had a separate, unrelated bug that also caused transparent chats in the timeframe of the reports I linked earlier from Firefox and Safari. So far I have only seen reports of this latest one happening in Chrome.
,
Sep 28 2016
I have not seen the issue in the past few days using the latest M53 ChromeOS image.
,
Sep 29 2016
Marking unconfirmed because nobody has seen it recently. Somehow the first paint is getting lost, or the first paint is never happening. Apparently layout is done because you can click on things, but even then I suppose the layout might be done in response to the hit test. Adding scheduling and paint invalidation components.
,
Sep 29 2016
rohitbm@, can you reproduce recently?
,
Sep 29 2016
I haven't seen this issue lately on my Mac OS X either.
,
Sep 30 2016
,
Sep 30 2016
Issue 598043 was me making frames navigated back to "about:blank" actually blank out. That change was reverted, but maybe your frames are somehow ending up being at "about:blank"?
,
Sep 30 2016
It had been a while but I saw it once today on ChromeOS. Version 53.0.2785.144 beta (64-bit) Platform 8530.93.0 (Official Build) beta-channel
,
Sep 30 2016
The Reddit post linked in comment 15 is 162 days old, and is likely from a different that was in Hangouts that we fixed. From the Hangouts side, we have no recent reproes outside of Chrome, and the repro here is considerably different. The Reddit user's report is likely from those iframes not loading, whereas the issue we're seeing right now has the iframe loading but the content not showing. Users can actually interact with the UI within the apparently empty iframe.
,
Sep 30 2016
Hangouts iframes do not currently load about:blank at any point in their loading process, so Issue 598043 is unrelated.
,
Oct 8 2016
Thank you for providing more feedback. Adding requester "schenney@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 10 2016
Scheduling and Invalidation folks, can you think of anything we might be able to CHECK or otherwise add that would enable us to isolate the cause of this? It must be very rare.
,
Oct 11 2016
I used to see this all the time, so much that I turned off Hangouts in Gmail. I turned it back on again around Sept 25 to try and repro this, but I have not had it happen since then.
,
Oct 20 2016
This is still happening for a number of our users.
,
Oct 21 2016
I suspect this is https://bugs.chromium.org/p/chromium/issues/detail?id=637373, and because that bug is reliably reproducible, we should wait for a fix on that before taking time on this one. Assigning appropriately, feel free to re-assign.
,
Oct 23 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 23 2017
I'm gonna assume this was bug 637373 as I haven't heard any more reports about this. |
||||||||||||||||
►
Sign in to add a comment |
||||||||||||||||
Comment 1 by pawong@google.com
, Sep 15 2016