Status: Unconfirmed
Owner: ----
Labels: OS-Android Pri-2
New issue 131732 by
TodMicha...@gmail.com: Chrome Android Tabs freeze when
opening new tab from
news.google.com
http://code.google.com/p/chromium/issues/detail?id=131732
Chrome Version: June 6 2012 release
Application Version (from "Chrome Settings > About Chrome"):
URLs (if applicable):
https://news.google.com
From "Android Settings > About Phone/Tablet"
Build number: IML74K.US_epad-9.4.2.21-20120323
Device: ASUS Transformer Prime TF201-PAD-0214
Behavior in Android Browser (if applicable):
This has been a long standing problem since about 2 versions ago from
Chrome Beta for android on both my Transformer TF201 and TF101. It does NOT
occur on my Galaxy Nexus.
Issue: When viewing
https://news.google.com and opening an article, it
attempts to open article in a new tab. If you just click on the article
link the new tab attempts to open, spins to display, then "completes" but
has no content. At this point, every tab, including the original
news.google.com tab is inert. The only way to recover is to close every tab
and then open a new tab. A workaround is that if you long press the link
and then manually choose "open in new tab" it will work.
Known Steps to reproduce:
1) Have an ASUS Transformer (original or prime) on ICS with latest Chrome
2) Logon to
https://news.google.com (preferably under your sign in profile).
3) Choose an article and click it.
4) A new tab will open and the article will attempt to load.
5) After a few moments, the spinning "load" indicator on the tab will cease
but the tab will be blank.
6) All other open tabs will also now no longer work to load/refresh.
Workaround on the Transformer - do not click a link, long click link and
choose Open in new tab. (Of course if you forget to do this one time, you
are fubar)
NOTE: Effect is not seen on the Galaxy Prime -- that opens properly on a
simple link click.
NOTE: Effect is not seen on all pages with links. Many websites with links
that open to new tabs do work. It is seen every time on the
news.google.com
site.
NOTE: First BETA of Chrome back in February or so did not have this issue,
however, every subsequent release has had this.
Expected result:
See above
Actual result:
See above