On Tue, Oct 11, 2011 at 11:53 AM, Aryeh Gregor <[email protected]> wrote:
> On Tue, Oct 11, 2011 at 12:58 PM, Ryosuke Niwa <[email protected]> wrote: > >> It also means you can't support :read-write for contenteditable, because > >> that > >> would make selectors depend on style resolution. Is it just a > >> convenience measure so that you don't have to implement efficient > >> property inheritance a second time? Could you make the property > >> ignored in user stylesheets, at least, so that the only way authors > >> can make things editable is contenteditable/designMode? > > > > I wanted to get rid of it but couldn't due to compat. issue. There are > too > > many applications that depend on -webkit-user-modify at the moment. > >> > >> I really don't think we want to standardize this -- it's not something > >> authors > >> should be using CSS for. > > > > Right. I don't think we should but that doesn't mean we can drop the > > support. > > Is that WebKit-only content, or web content too? Could you turn it > off just for web content? Or do you not like introducing > discrepancies like that between webpages and other pages? > The last time I checked, both. - Ryosuke
