Compiling on Windows broken with --disable-necko-wifi set
Categories
(Toolkit :: Geolocation Provider, defect)
Tracking
()
| 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)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-esr140+
|
Details | Review |
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.
Comment 2•2 months ago
|
||
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.
Updated•1 month ago
|
Comment 3•1 month ago
|
||
: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.
| Assignee | ||
Updated•1 month ago
|
| Assignee | ||
Comment 4•1 month ago
|
||
That's a lot simpler than I had anticipated it would be, thank you. Could you also uplift it to 140 too pls.
Comment 8•1 month ago
|
||
Set release status flags based on info from the regressing bug 1900225
Updated•1 month ago
|
Comment 9•1 month ago
|
||
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?
Updated•1 month ago
|
| Assignee | ||
Comment 10•1 month ago
|
||
(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.
| Assignee | ||
Comment 11•1 month ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D300825
Updated•1 month ago
|
Comment 12•1 month ago
|
||
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
Updated•1 month ago
|
Updated•1 month ago
|
Comment 13•1 month ago
|
||
| uplift | ||
Updated•1 month ago
|
Updated•1 month ago
|
Description
•