- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Mar 2022 23:03:44 +0000
- To: public-css-archive@w3.org
I am a bit confused - and honestly also a bit dissatisfied - due to the short meeting discussion and quick resolution. Is this now disregarded because @emilio thinks a pseudo-element is not the right way to solve the use cases? Or is it deferred to a future spec.? It seems that he and formerly @gregwhitworth at least acknowledge that styling dragged elements is worthwhile. After a [previous meeting](https://github.com/w3c/csswg-drafts/issues/1703#issuecomment-776108309) I was asked to provide use cases which [I did](https://github.com/w3c/csswg-drafts/issues/1703#issuecomment-776248528). In the same comment I also explained why I believe a pseudo-element is the right approach to this rather than a pseudo-class (like the existing `:-webkit-drag` [mentioned earlier](https://github.com/w3c/csswg-drafts/issues/1703#issuecomment-776169588) by @progers). > <fremy> emilio: we could reuse `content` > <fremy> emilio: with only an image allowed but that isn't great Reusing `content` was [the idea](https://github.com/w3c/csswg-drafts/issues/1703#issuecomment-776248528), yes. I wouldn't restrict this to images, though, as there are use cases (like dragging a text selection) for the other values supported for it. > <fremy> iank_: we should also consider the thread model > <fantasai> s/thread/threat If this means security and privacy issues, then I agree that those need to be considered. Though so far I cannot think of any. So how can I further help to get this considered? Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1703#issuecomment-1076903353 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 March 2022 23:03:45 UTC