Issue 174482 in chromium: history.pushState causes momentary title flicker

42 views
Skip to first unread message

chro...@googlecode.com

unread,
Feb 5, 2013, 6:21:38 PM2/5/13
to chromi...@chromium.org
Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2 Area-Undefined

New issue 174482 by San0...@gmail.com: history.pushState causes momentary
title flicker
http://code.google.com/p/chromium/issues/detail?id=174482

Chrome Version : 25.0.1364.58 beta-m
URLs (if applicable) : http://html5.gingerhost.com/
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x:
IE 7/8/9:

What steps will reproduce the problem?
1. Go to a website that uses history.pushState
2. Click to navigate in order to invoke history.pushState
3. Observe the page title in the browser tab

What is the expected result?
No change in the title on the page tab

What happens instead?
An unwarranted - momentary flicker

Please provide any additional information below. Attach a screenshot if
possible.

chro...@googlecode.com

unread,
Feb 11, 2013, 9:27:15 AM2/11/13
to chromi...@chromium.org
Updates:
Labels: Action-FeedbackNeeded Action-ReductionNeeded

Comment #1 on issue 174482 by manoranj...@chromium.org: history.pushState
San0013@, Can you please confirm us, still you are seeing this issue with
latest beta#25.0.1364.68 as well?

Thanks in advance!

chro...@googlecode.com

unread,
Feb 25, 2013, 8:46:32 AM2/25/13
to chromi...@chromium.org

Comment #2 on issue 174482 by bla...@layar.com: history.pushState causes
May be a duplicate of
http://code.google.com/p/chromium/issues/detail?id=50298

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

chro...@googlecode.com

unread,
Feb 25, 2013, 9:49:37 AM2/25/13
to chromi...@chromium.org

Comment #3 on issue 174482 by San0...@gmail.com: history.pushState causes
Re: #1 yes. with: 25.0.1364.97 beta-m
Re: #2 affirmative.
Reply all
Reply to author
Forward
0 new messages