Issue 106307 in chromium: tab onUpdated event with status = complete firing multiple times in a single page load

4 views
Skip to first unread message

chro...@googlecode.com

unread,
Dec 3, 2011, 9:29:17 PM12/3/11
to chromi...@chromium.org
Status: Unconfirmed
Owner: ----
Labels: OS-Mac Area-Undefined Pri-2 Type-Bug

New issue 106307 by a...@adambragg.com: tab onUpdated event with status =
complete firing multiple times in a single page load
http://code.google.com/p/chromium/issues/detail?id=106307

Chrome Version : 15.0.874.121
OS Version: OS X 10.7.2
URLs (if applicable) : facebook.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. Create and install the POC Extension as described here:
http://pastie.org/2962518
2. Visit Facebook.com
3. Observe the multiple onUpdated tab events fired with status = complete
in the background page console.

What is the expected result?
There should be only 1 tab onUpdated event with a status of complete.

What happens instead?
There are multiple tab onUpdated events with statuses = complete.

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

UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2)
AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.121 Safari/535.2


Attachments:
multipleCompletes.jpg 53.8 KB

chro...@googlecode.com

unread,
Dec 4, 2011, 6:54:51 AM12/4/11
to chromi...@chromium.org

Comment #1 on issue 106307 by orte...@gmail.com: tab onUpdated event with
status = complete firing multiple times in a single page load
http://code.google.com/p/chromium/issues/detail?id=106307

try out if you can recreate it using pushState()

chro...@googlecode.com

unread,
Dec 5, 2011, 3:11:45 PM12/5/11
to chromi...@chromium.org

Comment #2 on issue 106307 by a...@adambragg.com: tab onUpdated event with
status = complete firing multiple times in a single page load
http://code.google.com/p/chromium/issues/detail?id=106307

pushState() was the cause. I have added an enhancement request here:
http://goo.gl/69aui

chro...@googlecode.com

unread,
Jun 22, 2012, 9:48:05 PM6/22/12
to chromi...@chromium.org

Comment #4 on issue 106307 by andy.rut...@gmail.com: tab onUpdated event
with status = complete firing multiple times in a single page load
http://code.google.com/p/chromium/issues/detail?id=106307

It would be REALLY useful if the onUpdated event's changeInfo.status for a
history.pushState() could indicate that the modified URL did not cause a
document change - i.e. like Firefox's
webProgressListener.LOCATION_CHANGE_SAME_DOCUMENT

Reply all
Reply to author
Forward
0 new messages