- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Oct 2022 23:14:26 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-backgrounds] Are the rules for interactions of transforms and backgrounds on the root element what we want?`, and agreed to the following: * `RESOLVED: Always ignore transforms on backgrounds of the root element` * `RESOLVED: Always ignore transforms on backgrounds that propagate to canvas` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [css-backgrounds] Are the rules for interactions of transforms and backgrounds on the root element what we want?<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/6683<br> <dael> mattwoodrow: Looks like discussed last year, resolved to wait for filter spec<br> <dael> mattwoodrow: I would like to continue discussion and make a decision. No strong opinions<br> <dael> astearns: Can you get us up to speed with what has been discussed?<br> <dael> mattwoodrow: Current state is inconsistent between impl and spec is unclear which path. Pretty open. Slight diff in if background is fixed.<br> <dael> astearns: Anyone with opinions?<br> <dael> smaug: Any websites where this matters?<br> <smfr> s/smaug/smfr/<br> <dael> mattwoodrow: No one has found any. Poss because it's so different between browsers. I think Gecko never transforms, WebKit always, Chrome for scrolled but not fixed. No interop<br> <dael> smfr: I would argue to easiest to implement<br> <dael> astearns: Naive guess is that's never transform?<br> <dael> smfr: I think ignoring transform is easiest<br> <dael> fantasai: Could make sense b/c if you're transforming the whole root you could want a bg behind it and don't want that to transform with the page. Should be something behind it.<br> <dael> fantasai: If you want bg to transform with page you attach it to the page and get the behavior<br> <dael> smfr: Makes sense to me. I think only bg that prop to canvas?<br> <dael> fantasai: Yeah<br> <dael> smfr: I would say they never transform. If they want transform but bg on the body<br> <TabAtkins> This seems confusing in general, but I think the proposal makes sense<br> <dael> astearns: Anyone want to argue for paying attention to transforms on root element background?<br> <dael> astearns: Prop: Always ignore transforms on backgrounds of the root element<br> <dael> astearns: Is that sufficient resolution?<br> <dael> mattwoodrow: That's sufficient<br> <dael> smfr: That's both bg attachment fixed and scroll I think. But what you said should be sufficient<br> <dael> astearns: Objections?<br> <dael> RESOLVED: Always ignore transforms on backgrounds of the root element<br> <dael> florian: Question - do we mean bg on the root or bg that prop to the canvas? Do we mean those two?<br> <dael> fantasai: Yes. Anything prop to the canvas doesn't get impacted<br> <dael> fantasai: There's no transforms on canvas<br> <dael> astearns: Always ignore transforms on bg that get propagated to canvas<br> <dael> smfr: Transforms applied to elements. If it's prop to canvas bg not effected<br> <dael> fantasai: once prop to the canvas it's not impacted by any transforms<br> <dael> astearns: BG that are propagated to canvas have any transforms taken away<br> <dael> smfr: Render as if originating element had no transform<br> <dael> florian: We're clear enough. Let editors write<br> <dael> astearns: Current resolution + discussion or ammend the resolution?<br> <dael> florian: Another.<br> <florian> +1<br> <dael> astearns: Always ignore transforms on backgrounds that propage to canvas<br> <dael> RESOLVED: Always ignore transforms on backgrounds that propagate to canvas<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6683#issuecomment-1269092125 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 5 October 2022 23:14:28 UTC