- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Mar 2020 00:23:53 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[mediaqueries-5] Adding prefers-reduced-data as part of MQ5 FPWD`, and agreed to the following: * `RESOLVED: Add three issues to the ED` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [mediaqueries-5] Adding prefers-reduced-data as part of MQ5 FPWD<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/2370<br> <dael> Adam: Inspired by JS having similar things. Access to information about users like data saver on your phone wher eyou can say at a high level you want ot lose less data. Can reduce background activities. In JS we can be aware of this just like we can reduce motion.<br> <smfr> q+<br> <dael> Adam: If they're in 2G or paying for data or something like that. Proposal is a flag in CSS so we can make adjustments. Proposal JS is granual but CSS just needs on or off. Do they want to reduce or carry on undefined<br> <dael> Adam: Good intro?<br> <astearns> ack fantasai<br> <dael> astearns: Sure<br> <dael> fantasai: Good idea to have a MQ for this. Concern there is different levels of less data. One is I'm on a slow connection, another is I'm paying small data and want reduced functionality. I'm wondering if need a couple of levels. Reduce data and another to comprimise functionality<br> <fantasai> s/functionality/functionality if needed/<br> <dael> Adam: Good question. Reminds me of li-fi which is where it says you have wifi but you don't. Frustrating for user b/c what do you do. People can use things like service worker for that. CSS I'm not sure if we need more. I like we're mimicaing the system binary<br> <dael> Adam: Most questionable part of MQ is around how hard is it to use. Examples people put is I have a big BG image and people want to do a color but then browser has already loaded your image. Lot of potenial to not work. CSS b/c how it loads there's potential to not get wha tyou want.<br> <dael> Adam: Need to have a say where it goes. Maybe needs to be in head. MQ often bottom of file<br> <dael> TabAtkins: I suspect we don't need more levels right now because I don't see it being likely you have much you can do besides if it's not in data saver I load and if it's in mode I load colors. There's not much useful in CSS we can do. I suspect we just need the two. Load or don't load images<br> <dael> Adam: Fonts as well. You can load expensive custom fonts. Put behind the MQ and only load if they don't have preference<br> <dael> TabAtkins: Yeah. Yeah. Fonts and images. There isn't a middle ground. Either load or not<br> <astearns> ack smfr<br> <bkardell_> idk, I do both TabAtkins<br> <dael> smfr: Apple main concern is this is more fingerprinting. It's biased fingerprinting toward low income with limited data. We're concerned this could be a targetting vector.<br> <dael> smfr: iOS does have a settings switch but adds more fingerprinting where it remembers you flipped this switch on certain wifi. That's a worry.<br> <dael> smfr: Would like to see security and privacy section added to the spec<br> <dael> smfr: Not objecting but we do have concerns. Discussing if we would impl<br> <dael> TabAtkins: Are you impl the header?<br> <dael> smfr: I think answer is no<br> <dael> TabAtkins: Okay. You're not doing client hints that's acceptable problem<br> <astearns> ack fantasai<br> <Zakim> fantasai, you wanted to point out that media queries are not just CSS<br> <dael> fantasai: MQ aren't just CSS. Can also be accessed in JS and HTML attributes to load files. Not jsut about CSS but also controls if you load a JS library.<br> <dael> fantasai: Also these days not about if it's a BG image people are loading lots of videos for decoration and that's data that's not needed. Can replace that with an image. But if you're even more resource constrained you'd want an image<br> <chris> s/li-fi/lie-fi/<br> <fantasai> s/an image/no image/<br> <dael> fantasai: If we dn't have multiple levels now we should design so that we can expand later. I think there is multiple levels here and it's not just about CSS<br> <dael> Adam: Good examples. I like them<br> <dino> I'm not sure if the type of person who would load a huge video as a background image would also provide a fallback that is a solid colour :)<br> <dael> astearns: Hearing we need security and privacy section. Second is we should have separate issue about needing more then a binary state<br> <fantasai> dino, I can see AirBnB doing that, frex. They get pulled down over roaming connections a lot.<br> <dael> astearns: One bit of background. THis is on agenda b/c intent to prototype in Chrome<br> <dael> smfr: Would have liked to see discussion in WG before PR merged<br> <fantasai> +1 to smfr, adding features should get WG resolution<br> <dael> astearns: I think there was some but I agree there could have been more.<br> <dael> astearns: Looking through issue and not seeing discussion before merge, just comments on the issue<br> <dael> fantasai: Remove it from draft or add annotation on issues or don't leave indication that there's an issue in the draft<br> <dael> TabAtkins: I don't think we should remove given client hints serves the same data. Exposing to CSS is user friendliness. Precise design open issues on that. So long as client hints is going through I think we should have this in MQ as well<br> <dael> fantasai: We should annotate the issues a bit in the draft<br> <dael> TabAtkins: Yeah<br> <dael> smfr: Are client hints more than one impl? THe comparision isn't valid if blink is only browser that impl client hints<br> <dael> astearns: Anyone know the status in gecko?<br> <dael> ??: I believe we impl that<br> <dholbert> s/??/heycam/<br> <heycam> s/I believe/I don't believe/<br> <dael> astearns: Three issues. Security and privacy section. Add issue for more than binary. Add this is still under discussion and maybe not ready to ship<br> <dael> astearns: accurate?<br> <dael> Adam: Yes to me<br> <dael> chris: Question. Agenda item talks about if this should be in FPWD. That was published yesterday so whatever we decide will impact the ED. I think it was published with this included. I jsut took the ED and went forward<br> <dael> astearns: Yes, that's what you should have done. We can take it out if need be<br> <dael> astearns: Enough for now? Add the three issues to the draft and add them as separate GH issues<br> <dael> astearns: Prop: Add three issues to ED<br> <TabAtkins> Even in the "video vs img vs color" scenario, I don't think there's a particularly useful line to draw there. Basically, I don't think there's a particularly useful "I have plenty of data, but I'm not the *sultan*" line to use, at least in CSS. JS can do more complicated stuff, but I think in such a scenario you should downgrade all the way to a gradient or a very small image, if people are requesting reduced data at all.<br> <dael> RESOLVED: Add three issues to the ED<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2370#issuecomment-594960678 using your GitHub account
Received on Thursday, 5 March 2020 00:23:56 UTC