Re: [w3c/editing] Should browsers support ContentEditable for <option> elements? (#180)

@johanneswilm indeed, it is not something that we considered before when it comes to CE. Allowing the framework to do this sounds like a reasonable approach.
On the other hand, it does fall into the theme where we are trying to expose hooks to web developers to modify web content more easily. Allowing them to add/remove/edit option elements with some JS API would probably be more efficient than creating new elements and apppending them to the existing conrtol, the way it is currently done on the web. But I don't have a strong preference just considering different points of view.  @Leo7k sounds like you don't have a strong opinion on this either?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/180#issuecomment-451329893