Network Information API: missing downlink attribute causing infinite loading on ads.google.com
Categories
(Core :: DOM: Device Interfaces, defect)
Tracking
()
People
(Reporter: ksenia, Unassigned)
References
()
Details
As described here:
https://github.com/webcompat/web-bugs/issues/32982
Steps to reproduce:
On Firefox on Android sign in to your google account and go to the following link:
https://ads.google.com/aw/overview?ocid=338200999&__c=5875343151&authuser=0&__u=9047806137&mode=real&type=mobile&enableAllBrowsers=1&mobile=1
Expected:
Site loads
Actual:
Site doesn't load
Looks like even though window.navigator.connection
property exists in Firefox for Android, window.navigator.connection.downlink
is missing, which is causing the error, so the site never loads.
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Comment 2•5 years ago
|
||
I don't know but Daosheng will probably know.
Daosheng, also, can I file the request to make you the triage owner for Device Interfaces?
Comment 3•5 years ago
|
||
I think this is because Gecko hasn't implemented downlink
attribute in window.navigator.connection
yet [1]. We can consider to follow up the recent changes in Network Information API
from W3C draft [2].
:neha, I don't know anything about the roadmap of Device Interfaces, it is not covered by my radar.
[1] https://searchfox.org/mozilla-central/rev/b9041f813de0a05bf6de95a145d4e25004499517/dom/webidl/NetworkInformation.webidl#23
[2] http://wicg.github.io/netinfo/#networkinformation-interface
Comment 4•5 years ago
|
||
Google fixed the affected sites, so this is less pressing. Also, https://github.com/mozilla/standards-positions/issues/117
Updated•5 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 5•2 years ago
|
||
The severity field for this bug is relatively low, S3. However, the bug has 5 See Also bugs.
:cmartin, could you consider increasing the bug severity?
For more information, please visit auto_nag documentation.
Comment 6•2 years ago
|
||
Closing this bug as WONTFIX.
Google fixed the upstream problem, which is that their website didn't function properly without this API.
The second part of this is that we likely won't be implementing the Network Information API as-is, since Mozilla considers the standard itself to be "harmful".
Description
•