- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 Sep 2023 16:30:08 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-anchor-position-?] Add a ::tether pseudo-element`, and agreed to the following: * `RESOLVED: mark ::tether as at risk and leave note in the draft` <details><summary>The full IRC log of that discussion</summary> <bramus> TabAtkins: we had an issue about a way to style an arrow in response to abspos relative to anchor. this was more explicty in apple’s proposal with ::tether<br> <bramus> … this is a great idea.<br> <bramus> … having a border around the whole box + arrow seems like a need<br> <bramus> … but also very difficult<br> <bramus> … proposal to move to level 2<br> <bramus> … apple’s proposal had good <missed><br> <bramus> … to be clear it’s the styling, not the position<br> <bramus> … this might block us now, so like to push it furhter down the future<br> <bramus> astearns: are you talking about deferrint he styling or the ::tether allogehter?<br> <bramus> TabAtkins: the ::tether alltogehter. styling is essential and i think we need to get right<br> <florian> q+<br> <astearns> ack fantasai<br> <bramus> fantasai: curious to hear you expand a bit about styling that needs to be worked out<br> <astearns> for tooltips the tether (whether you can style it or not) seems pretty important<br> <bramus> TabAtkins: simple case: abspos is a solid bg with no border.tether is a triangle with same color. that is easy.<br> <bramus> … you might need to to a little bit of neg margin<br> <bramus> … hard part is a border or border-radius. getting tether to integrate with those and having border flow with it and not visibly be underneath it is hard to solve<br> <bramus> … and people want to do that based on existing example<br> <bramus> … also see examples outside of the web<br> <fremy> q+<br> <bramus> … i want to make sure we can handle that or recognize that we cant<br> <florian> q- later<br> <bramus> … border is the one that really bothers me. e.g non-linear border around anchor en tether<br> <bramus> fantasai: you can hack with drop shadows<br> <bramus> TabAtkins: a little bit<br> <bramus> fantasai: but i would like to do better<br> <bramus> … you can get pretty far with drop shadow, but do undrstand concern<br> <bramus> TabAtkins: potentially<br> <bramus> … needs more time to bake, and dont want to delete rest of the spec<br> <florian> q- later<br> <fantasai> s/delete/hold up/<br> <astearns> ack fremy<br> <kizu> q+<br> <bramus> fremy: similar question. i have impression that implementin tether itself is not a lot of work and will solve a lot of cases<br> <bramus> … maybe needs some trickery, but most cases it would solve the problem<br> <bramus> … you *want* a tether<br> <bramus> … do you really believe we need to defer, tab?<br> <bramus> … or do you believe it is too much effort?<br> <bramus> TabAtkins: if one feature takes a lot more work than rest of spec … don’t like to add things that will delay baking time<br> <bramus> … there are rendering concerns. As much as possible i would like tether to do right thing for authors and not give them a bad result to be angry about<br> <bramus> … we need a resonable rendering result with the styles in the UA. common cases should work out of the box<br> <bramus> …if we put it in L2 and do find it easy to solve, happy to pull it back into L1<br> <astearns> ack florian<br> <bramus> florian: I think agree with tab that this has extra complexity that will take time<br> <bramus> … but i don’t think we are at that point to go to CR yet, so seems premature to push it back now<br> <bramus> … even if incomplete, we should work together with the rest<br> <bramus> … as we evolve the spec, we should keep working with it<br> <fantasai> s/rest/rest, to ensure it all integrates together properly<br> <fantasai> +100 florian<br> <bramus> … my recommendatoin would be to keep it in for now with the understanding that impls might not start there and do the rest first, and spec wise it is not unlikely that we would evntually push it to L2<br> <astearns> we have a process for at-risk things<br> <bramus> kizu: other concerns outsid eof border issues<br> <bramus> … how to position it in more edge cases<br> <bramus> … is ok when position on TRBL<br> <bramus> … but on corners it is much more cmoplicated<br> <florian> s/we should keep working with it/we should keep working with it together with the rest, to make sure that the model stays coherent/<br> <bramus> … e.g. what if element is completely over other element? where to draw the tether and how to show it (pointing to left or right)<br> <bramus> … also depends on how we do fallback and conditional styling<br> <bramus> … tether with conditions maybe?<br> <bramus> … would be happy with basic implementation in L1 to be able to play with it<br> <astearns> q?<br> <bramus> … but lot of small issues –its a complicated topic<br> <astearns> ack kizu<br> <bramus> fantasai: agree with florian on keeping it in L1 that it helps us think about how it works with rest of styling model, e.g. fallback model<br> <TabAtkins> q+<br> <bramus> … how would that work with tether.<br> <astearns> ack TabAtkins<br> <bramus> … dont want to defer to L2, even if florian says it might end up there<br> <bramus> TabAtkins: I realize I am hypocretical at this as I dont like 2 levels of ED. Fine to not put it in L2, but want to mark it as risk in L1 saying that it is *super experimental*<br> <florian> seems fine to me<br> <bramus> proposed resolution: mark ::tether as at risk and leave not in the draft<br> <bramus> astearns: proposed resolution: mark ::tether as at risk and leave not in the draft<br> <florian> s/not in/note in/<br> <bramus> RESOLVED: mark ::tether as at risk and leave note in the draft<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9271#issuecomment-1721550220 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 15 September 2023 16:30:10 UTC