[Webkit-unassigned] [Bug 242006] REGRESSION (249800 at main): Cannot edit compose body field on outlook.com

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=242006

--- Comment #6 from Ryosuke Niwa <rniwa at webkit.org> ---
(In reply to Tim Nguyen (:ntim) from comment #5)
> (In reply to Ryosuke Niwa from comment #4)
> > So the current user-select: all behavior was specifically designed to be
> > used in Mail and other applications which want to treat an attachment file
> > as one non-editable thing that can be selected on its own.
> > 
> > It seems like `user-select: all` needs a different behavior but I agree with
> > you that making this change is quite risky in terms of backwards
> > compatibility. We may need to add SDK check or preserve the old behavior
> > just in `-webkit-user-select`.
> 
> I think we should just make the user-select behavior match other browsers,
> and have other applications use -webkit-user-modify to override editability.
> Other apps shouldn't hold back interopability on the web.

It's irresponsible to break iOS specific content or iOS applications like that. Think of end users who have been using an app suddenly faced with an erroneous behavior in new version of iOS.

> Preserving the old behavior for just -webkit-user-select wouldn't really
> help in this case, since both unprefixed and prefixed versions are used
> here, so the unprefixed version would win (even if not the case, the
> prefixed version is set to `auto` and not `all`).

I don't follow. They specify user-select and -webkit-user-select. If -webkit-user-select preserved the old behavior, then it would work precisely because it also specify user-select, which overrides the behavior of the prefixed version.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220625/afe7631b/attachment.htm>