No, I think it's still the geoclue responding late, given the 500ms delay happens synchronously: https://searchfox.org/firefox-main/rev/856a307913c2b73765b4e88d32cf15ed05549cae/dom/geolocation/Geolocation.cpp#746-758 We are calling dbus synchronously which is not great: https://searchfox.org/firefox-main/rev/856a307913c2b73765b4e88d32cf15ed05549cae/dom/system/linux/GeoclueLocationProvider.cpp#1004-1006 But other than that I think my opinion in comment #3 still holds: this is WPT not mochitest, we can't require such strict requirement to all implementations.
Bug 1964731 Comment 34 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
No, I think it's still the geoclue responding late, given the 500ms delay happens synchronously: https://searchfox.org/firefox-main/rev/856a307913c2b73765b4e88d32cf15ed05549cae/dom/geolocation/Geolocation.cpp#746-758 We are calling dbus synchronously which is not great: https://searchfox.org/firefox-main/rev/856a307913c2b73765b4e88d32cf15ed05549cae/dom/system/linux/GeoclueLocationProvider.cpp#1004-1006 But other than that I think my opinion in comment #3 still holds: this is WPT not mochitest, we can't apply such strict limitation to all implementations.