4 ms·

I keep hoping for the bluetooth api to be added at some point. Still unlikely unfortunately :-(

by JanSt 4y ago

akmarinov 4y ago
0 chance of that happening
- JanSt 4y ago
  yeah, apple is pretty stubborn on that one. I’m glad we have Chrome
  - hbn 4y ago
    The nice thing about Chrome is that any and every feature is implemented. The bad thing about Chrome is that any and every feature is implemented.
    - aeharding 4y ago
      There's still some things Safari prioritizes that other vendors don't have. For example, Chrome (and FF) still haven't fully implemented CSS colors level 4. Chrome and Firefox are still clamping all CSS colors to sRGB. You literally can't render anything outside of sRGB with CSS. And almost all modern Apple devices are capable of the display-p3 color space. This is very noticeable when rendering reds and greens, especially. https://webkit.org/blog/10042/wide-gamut-color-in-css-with-display-p3/ https://webkit.org/blog/10042/wide-gamut-color-in-css-with-d...
      - SemanticStrengh 4y ago
        this is not true anymore, chromium added support for other color spaces this year
        aeharding 4y ago
        Chrome supports CSS level 4 color functions, but they're clamped to sRGB. AKA, basically useless. https://bugs.chromium.org/p/chromium/issues/detail?id=1068610&q=srgb%20display-p3&can=2 https://bugs.chromium.org/p/chromium/issues/detail?id=106861... Edit: Actually, I don't think Chrome even supports CSS level 4 color functions. (It sounds like it's part of interop2022 though!)
        SemanticStrengh 4y ago
        Do you know when the clamping will be removed? I was referring to this https://chromestatus.com/feature/4592567062626304 https://chromestatus.com/feature/4592567062626304 Have I hallucinated? I wzs sure support for it was added recently Edit according to the last comment in the issue you linked, this is on the 2022 roadmap, it's about time to properly support HDR!
  - dmitriid 4y ago
    Both Safari and Firefox are stubborn on that one (and most other hardware APIs), and for good reasons.
    - whywhywhywhy 4y ago
      They can code working security models for other features so fingerprinting isn't a good reason. Firefox is actually looking at WebMidi now so they've clearly had a change of heart. Apple will never do it because it means you can make hardware devices that interact with iPhones without going through the App Store.
      - dmitriid 4y ago
        > They can code working security models for other features so fingerprinting isn't a good reason. And those working security models are? > Firefox is actually looking at WebMidi now so they've clearly had a change of heart. They didn't have a "change of heart". They most likely found a way to implement it the way it aligns with their position.
        JanSt 4y ago
        Pop up a dialog asking for permission to scan for devices.
        dmitriid 4y ago
        That's not a working security model when it's required for about a dozen such permissions (camera, mike, location, bluetooth, serial ports, midi, ambient light, gyroscopes, hid, ...) Chrome doesn't care and pushes these out. Safari and Mozilla: protections in these specs are inadequate for the large surface area and complexity that these APIs require
        mtomweb 4y ago
        That’s a week cop out from Apple when they offer far less protection in Native and allow apps to use Bluetooth to monitor your location. Web Bluetooth has much BETTER security and privacy than native. By not providing functionality it forces apps to use the AppStore.
olliej 4y ago
Yeah, I am forever thankful that my browser isn’t vending my Bluetooth devices to random websites. I don’t understand why so many people want so much of their machine state to be vended to random websites.
- JanSt 4y ago
  That's not how it would work. You would need to grant permission to websites and there are good use cases. No website could just randomly scan.
- mtomweb 4y ago
  Scanning is native only. Web Bluetooth does not slow scanning and you have to specify specific device categories or services to connect too without being able to work out what devices are there first. Read the security section on the Web Bluetooth spec.

I keep hoping for the bluetooth api to be added at some point. Still unlikely unfortunately :-(

by JanSt 4y ago

I keep hoping for the bluetooth api to be added at some point. Still unlikely unfortunately :-(

akmarinov 4y ago

0 chance of that happening

JanSt 4y ago
yeah, apple is pretty stubborn on that one. I’m glad we have Chrome
- hbn 4y ago
  The nice thing about Chrome is that any and every feature is implemented. The bad thing about Chrome is that any and every feature is implemented.
  - aeharding 4y ago
    There's still some things Safari prioritizes that other vendors don't have. For example, Chrome (and FF) still haven't fully implemented CSS colors level 4. Chrome and Firefox are still clamping all CSS colors to sRGB. You literally can't render anything outside of sRGB with CSS. And almost all modern Apple devices are capable of the display-p3 color space. This is very noticeable when rendering reds and greens, especially. https://webkit.org/blog/10042/wide-gamut-color-in-css-with-display-p3/ https://webkit.org/blog/10042/wide-gamut-color-in-css-with-d...
    - SemanticStrengh 4y ago
      this is not true anymore, chromium added support for other color spaces this year
      - aeharding 4y ago
        Chrome supports CSS level 4 color functions, but they're clamped to sRGB. AKA, basically useless. https://bugs.chromium.org/p/chromium/issues/detail?id=1068610&q=srgb%20display-p3&can=2 https://bugs.chromium.org/p/chromium/issues/detail?id=106861... Edit: Actually, I don't think Chrome even supports CSS level 4 color functions. (It sounds like it's part of interop2022 though!)
        SemanticStrengh 4y ago
        Do you know when the clamping will be removed? I was referring to this https://chromestatus.com/feature/4592567062626304 https://chromestatus.com/feature/4592567062626304 Have I hallucinated? I wzs sure support for it was added recently Edit according to the last comment in the issue you linked, this is on the 2022 roadmap, it's about time to properly support HDR!
- dmitriid 4y ago
  Both Safari and Firefox are stubborn on that one (and most other hardware APIs), and for good reasons.
  - whywhywhywhy 4y ago
    They can code working security models for other features so fingerprinting isn't a good reason. Firefox is actually looking at WebMidi now so they've clearly had a change of heart. Apple will never do it because it means you can make hardware devices that interact with iPhones without going through the App Store.
    - dmitriid 4y ago
      > They can code working security models for other features so fingerprinting isn't a good reason. And those working security models are? > Firefox is actually looking at WebMidi now so they've clearly had a change of heart. They didn't have a "change of heart". They most likely found a way to implement it the way it aligns with their position.
      - JanSt 4y ago
        Pop up a dialog asking for permission to scan for devices.
        dmitriid 4y ago
        That's not a working security model when it's required for about a dozen such permissions (camera, mike, location, bluetooth, serial ports, midi, ambient light, gyroscopes, hid, ...) Chrome doesn't care and pushes these out. Safari and Mozilla: protections in these specs are inadequate for the large surface area and complexity that these APIs require
        mtomweb 4y ago
        That’s a week cop out from Apple when they offer far less protection in Native and allow apps to use Bluetooth to monitor your location. Web Bluetooth has much BETTER security and privacy than native. By not providing functionality it forces apps to use the AppStore.

olliej 4y ago

Yeah, I am forever thankful that my browser isn’t vending my Bluetooth devices to random websites. I don’t understand why so many people want so much of their machine state to be vended to random websites.

JanSt 4y ago
That's not how it would work. You would need to grant permission to websites and there are good use cases. No website could just randomly scan.
mtomweb 4y ago
Scanning is native only. Web Bluetooth does not slow scanning and you have to specify specific device categories or services to connect too without being able to work out what devices are there first. Read the security section on the Web Bluetooth spec.