Closed Bug 2036676 Opened 2 months ago Closed 1 month ago

Compiling on Windows broken with --disable-necko-wifi set

Categories

(Toolkit :: Geolocation Provider, defect)

Firefox 150
defect

Tracking

()

RESOLVED FIXED
152 Branch
Tracking Status
firefox-esr115 --- unaffected
firefox-esr140 --- fixed
firefox150 --- wontfix
firefox151 --- wontfix
firefox152 --- fixed

People

(Reporter: k4sum1, Assigned: handyman)

References

(Regression)

Details

(Keywords: regression)

Attachments

(2 files)

Steps to reproduce:

Add ac_add_options --disable-necko-wifi to mozconfig and start compiling.

Actual results:

Compiling fails with nsIWifiListener.h not found.

Expected results:

Browser should compile without errors.

Not entirely sure where to put this part as I have no additional information box to type in, so new comment it is.

I've traced it to Bud 1900225, and specifically part 5 and part 6. The code was written with the assumption that the necko wifi scanner will always be available, and in this case it is not. For my fork, I've found this workaround for successful builds. https://github.com/Eclipse-Community/r3dfox/commit/be22ead533916ecc79419a2d50459da2b68ac6d2

I figure since it should be a supported build flag, I'd open this issue and see if it will get fixed. Affected versions include ESR 128. ESR 140, and latest 150.

The Bugbug bot thinks this bug should belong to the 'Toolkit::Add-ons Manager' component, but is not confident enough to move the bug to that component.

Component: Untriaged → General
Product: Firefox → Firefox Build System
Component: General → DOM: Geolocation
Keywords: regression
Product: Firefox Build System → Core
Regressed by: 1900225

:handyman, since you are the author of the regressor, bug 1900225, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Flags: needinfo?(davidp99)
Assignee: nobody → davidp99
Flags: needinfo?(davidp99)
Pushed by daparks@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/9e104dc96f58 https://hg.mozilla.org/integration/autoland/rev/d50ebbfcb25a Use basic GeolocationSystem implementation when NECKO_WIFI is not defined r=jjaschke

That's a lot simpler than I had anticipated it would be, thank you. Could you also uplift it to 140 too pls.

Status: UNCONFIRMED → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 152 Branch

Set release status flags based on info from the regressing bug 1900225

Component: DOM: Geolocation → Geolocation Provider
Product: Core → Toolkit

I think we should probably think about removing wifi scanning than requiring wifi, is scanning wifi the only way to prompt geolocation? Can we call geolocation API instead?

Flags: needinfo?(davidp99)

(In reply to Kagami Rosylight [:saschanaz] (they/them) from comment #9)

I think we should probably think about removing wifi scanning than requiring wifi, is scanning wifi the only way to prompt geolocation? Can we call geolocation API instead?

Filed bug 2040528 for this.

Flags: needinfo?(davidp99)
Attachment #9587494 - Flags: approval-mozilla-esr140?

firefox-esr140 Uplift Approval Request

  • User impact if declined/Reason for urgency: Repo doesn't build with --disable-necko-wifi set
  • Code covered by automated testing?: yes
  • Fix verified in Nightly?: yes
  • Needs manual QE testing?: no
  • Steps to reproduce for manual QE testing:
  • Risk associated with taking this patch: low
  • Explanation of risk level: This change only affects builds that set --disable-necko-wifi. It disables some of the Windows geolocation UX in those builds. Previously, those builds would not compile.
  • String changes made/needed?: N/A
  • Is Android affected?: no
Attachment #9587494 - Flags: approval-mozilla-esr140? → approval-mozilla-esr140+
QA Whiteboard: [qa-triage-done-c153/b152]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: