Page MenuHomePhabricator

[web] [refactor] move default input styling to input component
AbandonedPublic

Authored by benschac on Feb 25 2022, 11:17 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Jan 6, 11:42 PM
Unknown Object (File)
Mon, Jan 6, 11:41 PM
Unknown Object (File)
Mon, Jan 6, 11:35 PM
Unknown Object (File)
Sun, Jan 5, 4:18 AM
Unknown Object (File)
Sat, Jan 4, 3:28 AM
Unknown Object (File)
Sat, Jan 4, 3:27 AM
Unknown Object (File)
Fri, Dec 27, 8:22 AM
Unknown Object (File)
Fri, Dec 27, 8:21 AM

Details

Reviewers
atul
Summary

we should only be using input components and their styling. Moving the global input styling and moving it to the input component.

before:

Image 2022-02-25 at 2.17.55 PM.jpg (826×1 px, 85 KB)

after:
Image 2022-02-25 at 2.17.39 PM.jpg (768×1 px, 81 KB)

Test Plan

look at input component. They're still not styled 100%, but they shouldn't change. https://developer.mozilla.org/en-US/docs/Web/CSS/appearance appearance properties are just removing default browser styling.

Diff Detail

Repository
rCOMM Comm
Branch
fix-border-radius
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

atul requested changes to this revision.Mar 2 2022, 8:05 AM
atul added inline comments.
web/style.css
30–32

Moving the global input styling and moving it to the input component.

Then why are we keeping styles like border and border-radius?

Don't these styles also affect the <textarea> tag? Are you sure we want to be removing these styles for that as well? Or should we break this into two separate selectors (one for input and another for textarea)?

This revision now requires changes to proceed.Mar 2 2022, 8:05 AM
benschac added inline comments.
web/style.css
30–32

Yeah, I should break these styles out a bit more. I don't think they really do anything. But you make a good point that this will also effect textarea elements.