LibWeb: Make reference to global in report timing steps non-const

Marking a resource timing entry requires calling non-const methods on
the global object to append to the performance buffer.
This commit is contained in:
Luke Wilde 2025-02-26 15:02:49 +00:00 committed by Andrew Kaster
parent 67cfb64d07
commit 618697ef13
Notes: github-actions[bot] 2025-03-06 16:02:11 +00:00
3 changed files with 6 additions and 6 deletions

View file

@ -35,12 +35,12 @@ public:
[[nodiscard]] static GC::Ref<FetchController> create(JS::VM&);
void set_full_timing_info(GC::Ref<FetchTimingInfo> full_timing_info) { m_full_timing_info = full_timing_info; }
void set_report_timing_steps(Function<void(JS::Object const&)> report_timing_steps);
void set_report_timing_steps(Function<void(JS::Object&)> report_timing_steps);
void set_next_manual_redirect_steps(Function<void()> next_manual_redirect_steps);
[[nodiscard]] State state() const { return m_state; }
void report_timing(JS::Object const&) const;
void report_timing(JS::Object&) const;
void process_next_manual_redirect() const;
[[nodiscard]] GC::Ref<FetchTimingInfo> extract_full_timing_info() const;
void abort(JS::Realm&, Optional<JS::Value>);
@ -73,7 +73,7 @@ private:
// https://fetch.spec.whatwg.org/#fetch-controller-report-timing-steps
// report timing steps (default null)
// Null or an algorithm accepting a global object.
GC::Ptr<GC::Function<void(JS::Object const&)>> m_report_timing_steps;
GC::Ptr<GC::Function<void(JS::Object&)>> m_report_timing_steps;
// https://fetch.spec.whatwg.org/#fetch-controller-report-timing-steps
// serialized abort reason (default null)