Comment by blue_pants
Comment by blue_pants a day ago
What about <permission> having browser-defined UI instead? A site needs to access the location, for example there's a button on the page, 'Show my location', which is wrapped in a <permission> tag. When the user hovers over the button, the browser UI would appear on top of the area with a lock or something (the site cannot style this UI). If the user clicks on it, it would show the usual 'Site wants to use your location', and if the user agrees, they can click on the 'Show my location' button, if they don't agree, the browser UI would be shown again on the next hover. It would make it impossible for sites to obscure the permission-requesting UI.
Olx.in
Original fb marketplace in india.
These fuckers ask for location on each search query, basically on each page load.
It is annoying to operate on Firefox focus and regular Firefox on android as it has a bug I assume that does not honor per site permission disable request.
Same on Firefox desktop, it works, sometimes it does not and then the site is unusable unless you deny location on each page load. Urrrghhh
We need global default off and per site permission.
Also, would it not be easier to pass dummy coordinates like 0.00,0.00 to bypass the nag screen ?
Same for notifications. "Yeah yeah notifications are enabled. Stop bothering me" ??