Open
Bug 956287
Opened 11 years ago
Updated 2 years ago
Developer Tools: Network Monitor: webm request disappears from the request list
Categories
(DevTools :: Netmonitor, defect)
DevTools
Netmonitor
Tracking
(Not tracked)
NEW
People
(Reporter: thomas, Unassigned)
References
(Blocks 1 open bug)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:26.0) Gecko/20100101 Firefox/26.0 (Beta/Release)
Build ID: 20131205075310
Steps to reproduce:
1. Open Developer Tools / Network panel
2. Request this url: http://zippy.gfycat.com/ThreadbareCompetentEastrussiancoursinghounds.webm
Actual results:
The request is added to the list for a brief moment, then disappears from the list.
Expected results:
The request should be displayed in the list until a new document is requested.
As this video {http://media.w3.org/2010/05/sintel/trailer.webm} seems to create the expected result is seems like there is some special configuration on the gfycat server.
Firebug: Gives the expected result
Chrome DevTools Adds two requests (where the first says '(canceled)'
cURL command for further inspection,
curl -s -D - http://zippy.gfycat.com/ThreadbareCompetentEastrussiancoursinghounds.webm -o /dev/null
Reporter | ||
Comment 1•11 years ago
|
||
Note: tested with filter set to 'All'
Comment 2•11 years ago
|
||
Was able to reproduce on Firefox 26 and latest Nightly using Mac OS X 10.9, Windows 7x32 and Ubuntu 13.04x32.
Status: UNCONFIRMED → NEW
Component: Untriaged → Developer Tools: Netmonitor
Ever confirmed: true
OS: Mac OS X → All
Hardware: x86 → All
Version: 26 Branch → Trunk
Reporter | ||
Comment 3•11 years ago
|
||
This happens when the webm file is loaded to the browser
You can see this by opening the Network tab and load the w3c video mentioned previously.
Watch the download progress bar in the video element. When the load is completed, the file disappears from the Network list.
Updated•7 years ago
|
Product: Firefox → DevTools
Updated•5 years ago
|
Blocks: missing-incomplete-dup-requests
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•