3 ms·

Can you give examples?

• eternityforest 5y ago
  Battery Status API, Ambient Light are the two big Mozilla examples I know, but I suspect the list may be fairly long. I believe they are also against web bluetooth and serial. Apple has some permission stuff that apparently degrades Tile on their platforms IIRC.
  • olliej 5y ago
    There is no reason for any of those to be exposed to the web. For web specs you can't just think "I could do this cool thing", you have to say "what can a random popup ad do with this". Our experience with WebGL shows permission dialogs are a bad experience, and people will also click "yes" to make them go away. Most users report "would you like notifications" from websites as being spam/annoying.
    • eternityforest 5y ago
      When the only consequence is being tracked, it's mostly fine if people just click yes. It's generally common knowledge that all sites are tracking you in all ways that they can and any time they ask for a permission it's to spy on you. Users who actually are more concerned with privacy probably will not click every random button. Which is in itself one bit of trackable information, but that's about it. Battery status is very useful for kiosk applications. Web Bluetooth is obviously great for all kinds of IoT things. The more dangerous ones like Bluetooth can require you to explicitly select a target, and most people will notice something is wrong if they see MyBonerBest.io wants to connect to a list that includes their watch and light bulbs. EU Cookie consent is somewhat changing that all, by training people to click yes on prompts faster than their eyes could even focus on them. If there is a risk, it's probably more that people click out of reflex than out of not understanding, which can be partly mitigated with improved UI.