Bug 231565

Summary: Add an override stylesheet for the alternate form control design
Product: WebKit Reporter: Tim Horton <thorton>
Component: New BugsAssignee: Tim Horton <thorton>
Status: RESOLVED FIXED    
Severity: Normal CC: akeerthi, dino, hi, webkit-bug-importer, wenson_hsieh
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch none

Tim Horton
Reported 2021-10-12 01:33:10 PDT
Add an override stylesheet for the alternate form control design
Attachments
Patch (3.94 KB, patch)
2021-10-12 01:34 PDT, Tim Horton 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Tim Horton
Comment 1 2021-10-12 01:34:32 PDT
Created attachment 440907 [details] Patch
Radar WebKit Bug Importer
Comment 2 2021-10-12 01:35:13 PDT
<rdar://problem/84137252>
Devin Rousso
Comment 3 2021-10-12 11:20:57 PDT
Comment on attachment 440907 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=440907&action=review r=me > Source/WebCore/DerivedSources.make:1587 > +POSSIBLE_ADDITIONAL_USER_AGENT_STYLE_SHEETS = \ `POSSIBLE` makes it sound like not all of the things in this list will actually exist. Is that accurate? Would `RESOLVED` be a better name?
Tim Horton
Comment 4 2021-10-12 11:22:51 PDT
(In reply to Devin Rousso from comment #3) > Comment on attachment 440907 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=440907&action=review > > r=me > > > Source/WebCore/DerivedSources.make:1587 > > +POSSIBLE_ADDITIONAL_USER_AGENT_STYLE_SHEETS = \ > > `POSSIBLE` makes it sound like not all of the things in this list will > actually exist. Is that accurate? Would `RESOLVED` be a better name? The name matches the media controls one that is adjacent. But, maybe?
EWS
Comment 5 2021-10-12 13:08:22 PDT
Committed r284008 (242850@main): <https://commits.webkit.org/242850@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 440907 [details].
Note You need to log in before you can comment on or make changes to this bug.