- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Dec 2023 17:18:37 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[mediaqueries-5] Media query for enclosed screens`. <details><summary>The full IRC log of that discussion</summary> <TabAtkins> fantasai: for virtual headset displays, there might be some things that are different from regular displays an author will care about<br> <TabAtkins> fantasai: We have several MQs already - pointer, hover, environment-blending<br> <TabAtkins> fantasai: One thing that came up is whether you can scan a QR code on the page - if you're on a headset, your phone can't be used to scan something on the page<br> <bkardell_> q+<br> <TabAtkins> fantasai: So q is if we should add this, and if so, what to call it?<br> <astearns> ack bkardell_<br> <TabAtkins> bkardell_: Whether you can scan a qr code is something people want to do with..<br> <TabAtkins> bkardell_: igalia makes a vr browser<br> <TabAtkins> bkardell_: used on many enclosed-screen browsers<br> <TabAtkins> bkardell_: The fact that you can't scan the obvious way doesn't mean there won't be a way to do it<br> <TabAtkins> bkardell_: The browser might offer a way to follow a qr code itself<br> <florian> q+<br> <TabAtkins> fantasai: In general, you can't take a photo of the scren with another device<br> <TabAtkins> bkardell_: Not directly, but you can cast to another device<br> <TabAtkins> fantasai: At that point you have another device and it can resolve the MQs differently<br> <astearns> ack florian<br> <TabAtkins> bkardell_: Well, not if it's like ChromeCast<br> <TabAtkins> florian: Need to be careful about the "cast" situation<br> <TabAtkins> florian: In the flip way, you think if you're *not* in an enclosed screen you want to hide passwords by default, but show when you are in an enclosed screen because nobody can see<br> <TabAtkins> florian: But if casted they can<br> <TabAtkins> florian: So does it mean people *probably* can't see your screen? Or *definitely* can't?<br> <TabAtkins> florian: Think we need to know more about the intended use-cases (plural) to know how they expect to behave<br> <TabAtkins> bkardell_: Yes, agreed. There's "pass-thru" on devices; on a Quest it's not good enough for photos, but for others...<br> <TabAtkins> bkardell_: Might be good to bring to Immersive Web group. Happy to talk more offline.<br> <TabAtkins> bkardell_: I think there def are some more MQs to do here<br> <TabAtkins> astearns: Sounds like we should take this back to the issue and explore the specific use-cases in more detail.<br> <TabAtkins> astearns: Is that ok?<br> <TabAtkins> fantasai: I think that's fine. Main thing from our side is the QR code issue.<br> <TabAtkins> bkardell_: Explain that?<br> <TabAtkins> fantasai: You ahve an app, can send info or auth yourself by scanning a QR code with your phone and it'll link accounts<br> <TabAtkins> fantasai: But you can't do that if you're on a headset<br> <fantasai> TabAtkins: The phone is the thing that needs to see the QR code, doesn't matter if the headset can scan it<br> <fantasai> TabAtkins: so that e.g. you can link your phone chat with desktop chat<br> <fantasai> TabAtkins: This is not handled by the browser on the headset being able to do anything<br> <fantasai> bkardell_: the browsers on both devices can talk to each other<br> <TabAtkins> bkardell_: Those devices generally have some way to send info to another device. We should talk offline<br> <TabAtkins> astearns: In the cases I can think of, where scanning a QR code is necessary, there's usually an alternate provided bc not everyone has a second device.<br> <TabAtkins> astearns: We'll take it back to the issue and explore the use-cases.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9701#issuecomment-1854400034 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 13 December 2023 17:18:39 UTC