Page MenuHomePhabricator

[web] [fix] [ENG-1033] change modal x default to show on default
ClosedPublic

Authored by benschac on Apr 22 2022, 2:39 PM.
Tags
None
Referenced Files
F3389145: D3820.diff
Fri, Nov 29, 5:46 PM
Unknown Object (File)
Fri, Nov 8, 10:43 PM
Unknown Object (File)
Tue, Nov 5, 3:45 AM
Unknown Object (File)
Tue, Nov 5, 3:45 AM
Unknown Object (File)
Tue, Nov 5, 3:45 AM
Unknown Object (File)
Tue, Nov 5, 3:45 AM
Unknown Object (File)
Tue, Nov 5, 3:44 AM
Unknown Object (File)
Oct 8 2024, 12:16 AM

Details

Summary
Test Plan

all modals should have the x button by default. attaching screen shots.

Diff Detail

Repository
rCOMM Comm
Branch
benjamin/eng-1033-close-button-removed-from-modal
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

benschac edited the summary of this revision. (Show Details)

Should you also go back and explicitly set withCloseButton to false for the modals you decided didn't need a close button?

This revision is now accepted and ready to land.Apr 24 2022, 2:27 PM
web/modals/threads/confirm-leave-thread-modal.react.js
21 ↗(On Diff #11914)

After looking through the codebase. The modal component is used in 16 places. The only place so far that looks like it doesn't call for an 'x' is the leaving thread modal, per the design.

In D3820#106142, @atul wrote:

Should you also go back and explicitly set withCloseButton to false for the modals you decided didn't need a close button?

Addressed this in the inline comment.

@atul -- can you take another look?

atul added inline comments.
web/modals/threads/confirm-leave-thread-modal.react.js
21 ↗(On Diff #11914)

The only place so far that looks like it doesn't call for an 'x' is the leaving thread modal, per the design.

Makes sense. Personally curious if omitting the close button for this modal was intentional or an oversight... but seems fine to me either way.

This revision is now accepted and ready to land.Apr 26 2022, 7:55 AM