Closed Bug 1665078 Opened 4 years ago Closed 4 years ago

Test failed: wpt/resource-timing/buffer-full-then-increased

Categories

(Core :: DOM: Core & HTML, defect)

80 Branch
defect

Tracking

()

RESOLVED DUPLICATE of bug 1665075

People

(Reporter: noam.helfman, Unassigned)

Details

Steps to reproduce:

Follow https://github.com/web-platform-tests/wpt steps to setup test env
wpt serve
Open:
http://web-platform.test:8000/resource-timing/buffer-full-then-increased.html

Actual results:

Test failure with the following message:

Fail	Test that overflowing the buffer and immediately increasing its limit does not trigger the resourcetimingbufferfull event	assert_equals: All resources should be in the buffer, since its size was increased expected 3 but got 0

testThatBufferContainsTheRightResources@http://web-platform.test:8000/resource-timing/buffer-full-then-increased.html:29:22
@http://web-platform.test:8000/resource-timing/buffer-full-then-increased.html:40:5

Expected results:

Test pass:

Pass	Test that overflowing the buffer and immediately increasing its limit does not trigger the resourcetimingbufferfull event

Setting a component for this issue in order to get the dev team involved.
If you feel it's an incorrect one please feel free to change it to a more appropriate one.

Component: Untriaged → DOM: Core & HTML
Product: Firefox → Core

Since both trigger the same resourcetimingbufferfull event, let's track this in the previous bug:

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.