Closed Bug 1513472 Opened 7 years ago Closed 6 years ago

make hero recording more generic

Categories

(Testing :: Raptor, enhancement, P2)

Product:
Testing
Component:
Raptor
Version:
Version 3
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: Bebe, Unassigned)

References

Details

Currently we need to modify mitmproxy recordings to add specific hero elements to the web pages. As hero elements are just searching for a specific tag in the tested webpage, update the hero recording process to search for a provided element. See: https://searchfox.org/mozilla-central/source/testing/raptor/webext/raptor/measure.js#109 Currently we search for elements that have 'elementtiming' attribute and calculate when they are available. We could do the same thing with any CSS element. This change would improve the test development/recording process and also verify a unmodified web page.
:davehunt :rwood what do you think about this?
Flags: needinfo?(rwood)
Flags: needinfo?(dave.hunt)
Thanks for raising this, I do agree this would be a good enhancement. Given the issues reported about hero element timing (bug 1510999) and discussions in Mozlando about using alternate metrics for page loads (bug 1504013), I think we should hold off working on this for now.
Flags: needinfo?(dave.hunt)
Priority: -- → P2
Flags: needinfo?(rwood)
Blocks: 1509925

There are no request for hero elements at this time.
Closing this as won't fix

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