[Webkit-unassigned] [Bug 56979] New: Expose 'isUserEditable()' (conceptually) in Chromium WebKit API

[bugzilla-daemon at webkit.org]

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

           Summary: Expose 'isUserEditable()' (conceptually) in Chromium
                    WebKit API
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit API
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: isherman at chromium.org
                CC: fishd at chromium.org, dglazkov at chromium.org,
                    jamesr at chromium.org, isherman at chromium.org


See https://bugs.webkit.org/show_bug.cgi?id=56809 for some backstory.

For Chromium Autofill, we need a concept akin to "Is this field user-editable?"  Currently, we approximate this by checking that the field is (a) enabled, (b) not read only, and (c) focusable.  (c) is particularly odd, as we call into HTMLFormControlElement::isFocusable(), which assumes that layout has been done -- but does not do the layout itself.  It might be wise to encapsulate this or similar "isUserEditable()" logic within WebKit, and expose that one method in the API.  Otherwise, we should re-evaluate whether we are exposing the right methods, especially with the implicit dependency on layout having already occurred.  James also mentioned that reentrancy might be an issue to watch out for here.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.