3 ms·
If you get this error, you intentionally broke your browser, or are using a browser which doesn't support standard, essential functionality. This is not the sam
by modeless 4y ago
If you get this error, you intentionally broke your browser, or are using a browser which doesn't support standard, essential functionality. This is not the same thing as declining or blocking geolocation permission, which is supported and does not cause errors.
This specific error means you deleted the standard functions that implement the geolocation API, which is a completely different thing. That's fine too, you're welcome to browse the web with a broken configuration, but you have to realize that it will break things. You're not automatically entitled to request that every site support your broken configuration. It should also be noted that browsing with a non-default configuration like this makes you an easy target for fingerprinting.
Note that the site absolutely requires some form of geolocation to work at all. Satellite viewing times are location specific and without a precise location the site can't show you anything useful.
- jason-phillips 4y ago> This specific error means you deleted the standard functions that implement the geolocation API That's a rather flimsy straw man. I did no such thing. > You're not automatically entitled to request that every site support your broken configuration. Goodness, now I'm entitled. I did no such thing; I just said that blaming your users for your sloppy coding is a terrible strategy.
- modeless 4y agoYou say you're using iOS Safari. I'm interested to know how you were able to configure it to delete navigator.geolocation, apparently without realizing what you were doing. I don't plan to support a broken configuration like that, but if you can figure out the cause then I could file a WebKit bug on your behalf.
- kortilla 4y agoWhy would it be on OP’s behalf? If it’s just a configuration that WebKit supports it’s either violating the standard or you’re not handling it correctly on your site. It has nothing to do with the OP at that point.
- modeless 4y agoThey are the one experiencing the bug. I can't file the bug because I don't know and can't investigate the cause. If they are experiencing an issue, and they find the cause, they should file the bug. But they probably won't bother, seeing as they'd rather blame me. I'm willing to file it for them, and that's probably better anyway as I have WebKit committer status. Bugs filed by me may have more weight as I have filed and fixed many before.
- ipaddr 4y agoYou really should be checking if the location object exists. Pushing the blame to another project is deflecting from a missing check that should happen on your end.
- modeless 4y agoRegardless of whether you agree with what I'm doing, you should agree that WebKit should not delete navigator.geolocation in any configuration. It's a clear fingerprinting issue.
- xattt 4y ago> Note that the site absolutely requires some form of geolocation to work at all. You should be able to specify a viewing location if geolocation is blocked.
- modeless 4y ago> This is not the same thing as declining or blocking geolocation permission, which is supported and does not cause errors.
- huhtenberg 4y agoGet off your high horse, you are wrong here. > If you get this error, you intentionally broke your browser, What I did was that I went into browser's preferences and set "geo.enabled" to false. > Note that the site absolutely requires some form of geolocation to work at all. Oh, please, I am perfectly capable of finding my village on the globe by hand.