New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 650145 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Oct 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: ----



Sign in to add a comment

Anomaly in Google Chrome(Android) Tab Counter

Reported by rajputut...@gmail.com, Sep 26 2016

Issue description

Device name:Micromax Q350

From "Settings > About Chrome"
Application version:51.02704.81
OS:Android 6.0;Micromax Q350 Build/MRA58K

URLs (if applicable):

Behavior in Android Browser (if applicable):
When scrolling through the webpages,the tab counter changes anomalously.



Steps to reproduce:
(1)Open any URL in Google Chrome(Android)
(2)Scroll Through the webpages.
(3)You will see that the tab counter(the square boundary) goes off and the number only gets displays as if its superscript(goes just above the Address box) 

Expected result:
The Box should be intact as it is,displaying the no. of tabs opened,while scrolling.

Actual result:
The Box disappears,only the Number(no of tabs open)displays,and becomes superscript.



 
IMG_20160926_114746_144.jpg
104 KB View Download
IMG_20160926_115413_780.jpg
47.2 KB View Download
Cc: ram...@chromium.org
Labels: triage-te

Comment 2 by ram...@chromium.org, Sep 26 2016

Labels: -triage-te Needs-Feedback
Not able to repro on Android one/MMX 42MB Android version MRA59G and Chrome stable '51.02704.81'
Are you able to repo this issue on latest M53 stable build from play store?

No,the bug was resolved.
thank you!!
Project Member

Comment 4 by sheriffbot@chromium.org, Oct 6 2016

Labels: -Needs-Feedback Needs-Review
Owner: ram...@chromium.org
Thank you for providing more feedback. Adding requester "ramine@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
Status: Verified (was: Unconfirmed)
Closing bug based on Comment 3, bug is resolved.

Sign in to add a comment