Bug 185018 - [Win] Implement corresponding changes in r231024 to move HTMLKeygenElement to client space
Summary: [Win] Implement corresponding changes in r231024 to move HTMLKeygenElement to...
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-25 17:33 PDT by Jiewen Tan
Modified: 2023-09-20 09:57 PDT (History)
7 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jiewen Tan 2018-04-25 17:33:17 PDT 
In r231024, the underlying operations of HTMLKeygenElement are moved from WebCore space/WebContent Process to Client space/UI Process. However, the Windows port is the forgotten. Filed this bug to keep track of the progress of Windows port corresponding changes.

The easiest way is to deprecate this element in Windows ports just like all other ports except macOS. macOS port has to support this because of legacy usages. Windows ports might not have to.
Comment 1 Jiewen Tan 2018-04-25 17:45:16 PDT 
Corresponding test expectations are updated in:
Committed r231036: <https://trac.webkit.org/changeset/231036>
Comment 2 Per Arne Vollan 2018-04-25 17:49:54 PDT 
(In reply to Jiewen Tan from comment #1)
> Corresponding test expectations are updated in:
> Committed r231036: <https://trac.webkit.org/changeset/231036>

Thanks for fixing this, Jiewen!
Comment 3 Ahmad Saleem 2023-09-20 09:02:18 PDT 
I think Keygen Element is gone so we don't have much to do here from Implementation perspective. We can mark this as 'RESOLVED WONTFIX', any thoughts?
Comment 4 Alexey Proskuryakov 2023-09-20 09:57:25 PDT 
Yes, and the test in question is gone too.