Open Bug 1381443 Opened 2 years ago Updated 5 months ago

Resource Timing API not showing correct resources in Selenium

Categories

(Core :: Networking, defect, P3)

56 Branch
defect

Tracking

()

People

(Reporter: shubham, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Whiteboard: [necko-next])

I have geckodriver latest version installed and I am running latest Firefox version. I wrote a selenium script to just open a URL in firefox and keep the browser open (I am not calling driver.close() or driver.quit())

Here is what the script looks like

    from selenium import webdriver
    driver = webdriver.Firefox()
    driver.get("https://www.nrk.no/")

The number of resources reported by Resource Timing API is > 100 for this website. Now, the website is just reloaded again, so that the resources are fetched from cache. NOTE: I refreshed by just pressing enter in the address bar

The number of resources reported by Resource Timing API is < 40. Same is the discrepancy with the number of resources in Developer Tools in Networks tab. This is happening for every website.

This is not happening if I just run plain Firefox and refresh the page in the same way. The resources number match always, irrespective of the number of times I refresh the web page.
This sounds like a resource timing API bug, I'm not sure how/if DevTools is involved here.
Component: Developer Tools → DOM
Product: Firefox → Core
Component: DOM → Networking
Whiteboard: [necko-next]
It's not even happening for Selenium. Here is the related issue with screenshots which I created after more testing

https://bugzilla.mozilla.org/show_bug.cgi?id=1385810
I'm fairly sure this is the same as bug 1113676. That stalled because I wasn't able to figure out what was causing some intermittent oranges. Maybe I can find the cycles to pick it up again.
Depends on: 1113676
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P2
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.