Matrix/element-web-Github
1
0
Fork 0
mirror of https://github.com/vector-im/element-web.git synced 2024-11-26 10:28:46 +08:00
Code Issues Packages Projects Releases Wiki Activity
6b384fe9c1
element-web-Github/res/css/components/views/settings/_AddRemoveThreepids.pcss

42 lines
968 B
Plaintext
Raw Normal View History

Move profile settings to a dedicated component The tab component is getting a bit hard to navigate
2019-01-23 04:28:33 +08:00
/*
Change license (#13) * Copyright headers 1 * Licence headers 2 * Copyright Headers 3 * Copyright Headers 4 * Copyright Headers 5 * Copyright Headers 6 * Copyright headers 7 * Add copyright headers for html and config file * Replace license files and update package.json * Update with CLA * lint
2024-09-09 21:57:16 +08:00
Copyright 2024 New Vector Ltd.
Move General user settings styles to more specific places This was w grab bag of styles for the email/phone components and one for something now in preferences. Move them elsewhere so I can rename the tab sensibly.
2024-08-01 23:45:56 +08:00
Copyright 2024 The Matrix.org Foundation C.I.C.
Change license (#13) * Copyright headers 1 * Licence headers 2 * Copyright Headers 3 * Copyright Headers 4 * Copyright Headers 5 * Copyright Headers 6 * Copyright headers 7 * Add copyright headers for html and config file * Replace license files and update package.json * Update with CLA * lint
2024-09-09 21:57:16 +08:00
Copyright 2019 New Vector Ltd
Improve the profile section a bit and add a highlight to the temp tab
2019-01-22 08:27:43 +08:00
Change license (#13) * Copyright headers 1 * Licence headers 2 * Copyright Headers 3 * Copyright Headers 4 * Copyright Headers 5 * Copyright Headers 6 * Copyright headers 7 * Add copyright headers for html and config file * Replace license files and update package.json * Update with CLA * lint
2024-09-09 21:57:16 +08:00
SPDX-License-Identifier: AGPL-3.0-only OR GPL-3.0-only
Please see LICENSE files in the repository root for full details.
Move profile settings to a dedicated component The tab component is getting a bit hard to navigate
2019-01-23 04:28:33 +08:00
*/
Bring in the change password section This also changes the layout slightly in the user settings, but nothing detrimental.
2019-01-23 04:09:40 +08:00
Move General user settings styles to more specific places This was w grab bag of styles for the email/phone components and one for something now in preferences. Move them elsewhere so I can rename the tab sensibly.
2024-08-01 23:45:56 +08:00
/*
Fix comment typos
2024-08-02 20:12:05 +08:00
* These used to live in General User Settings. These components are horribly duplicative
Move General user settings styles to more specific places This was w grab bag of styles for the email/phone components and one for something now in preferences. Move them elsewhere so I can rename the tab sensibly.
2024-08-01 23:45:56 +08:00
* but share the same styles. For now I'm putting them here so I can renamed the general
* tab sensibly and before I can refactor these components.
*/
Refactor the various email/phone management UI into a single component (#12884) * Refactor the various email/phone management UI into a single component These were basically the same component copied & pasted 3 times and tweaked to match the behaviour of each case. This de-dupes them into one component. This all could really benefit from playwright tests, but would require setting up a dummy ID server in the playwright tests. This is all legacy pre-MAS stuff so its questionable whether its worth the effort. * Basic test, remove old tests * Use different text to confirm remove & put headers back although the two texts are both 'Remove' in practice * Remove string This was never triggered anyway with sydent & synapse because they don't seem to agree on what error to return. In any case, I think it makes more sense for it to be consistent with the email path, ie. using a dialog. * Avoid nested forms * Snapshots * More snapshots * Test the hs side * Snapshots * Test IS bind/revoke * Test remove can be cancelled * Test unvalidated cases & fix phone error * Reset state between tests * Import useState directly * One more direct React import
2024-08-14 21:13:57 +08:00
.mx_AddRemoveThreepids_existing {
Merge styles of `_EmailAddresses.pcss` and `_PhoneNumbers.pcss` (#10679) * Rename: `mx_ExistingPhoneNumber_*` to `mx_PhoneNumber--existing_*` Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Rename: `mx_ExistingEmailAddress_*` to `mx_EmailAddress--existing_*` Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Merge styles for maitainability: `mx_GeneralUserSettingsTab_discovery_existing_*` `mx_EmailAddress--existing_*` and `mx_PhoneNumber--existing_*` adopt the same declarations, so maintaining them with common selectors should improve the maintainability. Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com * Rename: `mx_EmailAddress--existing_*` and `mx_PhoneNumber--existing_*` to `mx_GeneralUserSettingsTab_discovery_existing_*` Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Remove empty selectors Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Remove a duplicate selector: `.mx_GeneralUserSettingsTab_discovery--existing` Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Rename the button The button with the class name 'mx_GeneralUserSettingsTab_discovery_existing_button' is used for various types of action, so 'confirm' seems to be a bit misleading. Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Include: `mx_GeneralUserSettingsTab_discovery_existing_*` Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Run prettier Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * lint Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Review Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> --------- Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com
2023-05-03 19:34:32 +08:00
display: flex;
align-items: center;
}
Refactor the various email/phone management UI into a single component (#12884) * Refactor the various email/phone management UI into a single component These were basically the same component copied & pasted 3 times and tweaked to match the behaviour of each case. This de-dupes them into one component. This all could really benefit from playwright tests, but would require setting up a dummy ID server in the playwright tests. This is all legacy pre-MAS stuff so its questionable whether its worth the effort. * Basic test, remove old tests * Use different text to confirm remove & put headers back although the two texts are both 'Remove' in practice * Remove string This was never triggered anyway with sydent & synapse because they don't seem to agree on what error to return. In any case, I think it makes more sense for it to be consistent with the email path, ie. using a dialog. * Avoid nested forms * Snapshots * More snapshots * Test the hs side * Snapshots * Test IS bind/revoke * Test remove can be cancelled * Test unvalidated cases & fix phone error * Reset state between tests * Import useState directly * One more direct React import
2024-08-14 21:13:57 +08:00
.mx_AddRemoveThreepids_existing_address,
.mx_AddRemoveThreepids_existing_promptText {
Merge styles of `_EmailAddresses.pcss` and `_PhoneNumbers.pcss` (#10679) * Rename: `mx_ExistingPhoneNumber_*` to `mx_PhoneNumber--existing_*` Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Rename: `mx_ExistingEmailAddress_*` to `mx_EmailAddress--existing_*` Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Merge styles for maitainability: `mx_GeneralUserSettingsTab_discovery_existing_*` `mx_EmailAddress--existing_*` and `mx_PhoneNumber--existing_*` adopt the same declarations, so maintaining them with common selectors should improve the maintainability. Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com * Rename: `mx_EmailAddress--existing_*` and `mx_PhoneNumber--existing_*` to `mx_GeneralUserSettingsTab_discovery_existing_*` Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Remove empty selectors Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Remove a duplicate selector: `.mx_GeneralUserSettingsTab_discovery--existing` Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Rename the button The button with the class name 'mx_GeneralUserSettingsTab_discovery_existing_button' is used for various types of action, so 'confirm' seems to be a bit misleading. Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Include: `mx_GeneralUserSettingsTab_discovery_existing_*` Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Run prettier Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * lint Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Review Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> --------- Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com
2023-05-03 19:34:32 +08:00
flex: 1;
margin-right: 10px;
}
Refactor the various email/phone management UI into a single component (#12884) * Refactor the various email/phone management UI into a single component These were basically the same component copied & pasted 3 times and tweaked to match the behaviour of each case. This de-dupes them into one component. This all could really benefit from playwright tests, but would require setting up a dummy ID server in the playwright tests. This is all legacy pre-MAS stuff so its questionable whether its worth the effort. * Basic test, remove old tests * Use different text to confirm remove & put headers back although the two texts are both 'Remove' in practice * Remove string This was never triggered anyway with sydent & synapse because they don't seem to agree on what error to return. In any case, I think it makes more sense for it to be consistent with the email path, ie. using a dialog. * Avoid nested forms * Snapshots * More snapshots * Test the hs side * Snapshots * Test IS bind/revoke * Test remove can be cancelled * Test unvalidated cases & fix phone error * Reset state between tests * Import useState directly * One more direct React import
2024-08-14 21:13:57 +08:00
.mx_AddRemoveThreepids_existing_button {
Merge styles of `_EmailAddresses.pcss` and `_PhoneNumbers.pcss` (#10679) * Rename: `mx_ExistingPhoneNumber_*` to `mx_PhoneNumber--existing_*` Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Rename: `mx_ExistingEmailAddress_*` to `mx_EmailAddress--existing_*` Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Merge styles for maitainability: `mx_GeneralUserSettingsTab_discovery_existing_*` `mx_EmailAddress--existing_*` and `mx_PhoneNumber--existing_*` adopt the same declarations, so maintaining them with common selectors should improve the maintainability. Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com * Rename: `mx_EmailAddress--existing_*` and `mx_PhoneNumber--existing_*` to `mx_GeneralUserSettingsTab_discovery_existing_*` Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Remove empty selectors Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Remove a duplicate selector: `.mx_GeneralUserSettingsTab_discovery--existing` Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Rename the button The button with the class name 'mx_GeneralUserSettingsTab_discovery_existing_button' is used for various types of action, so 'confirm' seems to be a bit misleading. Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Include: `mx_GeneralUserSettingsTab_discovery_existing_*` Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Run prettier Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * lint Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> * Review Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> --------- Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com> Signed-off-by: Suguru Hirahara <luixxiul@users.noreply.github.com
2023-05-03 19:34:32 +08:00
margin-left: 5px;
}
Refactor the various email/phone management UI into a single component (#12884) * Refactor the various email/phone management UI into a single component These were basically the same component copied & pasted 3 times and tweaked to match the behaviour of each case. This de-dupes them into one component. This all could really benefit from playwright tests, but would require setting up a dummy ID server in the playwright tests. This is all legacy pre-MAS stuff so its questionable whether its worth the effort. * Basic test, remove old tests * Use different text to confirm remove & put headers back although the two texts are both 'Remove' in practice * Remove string This was never triggered anyway with sydent & synapse because they don't seem to agree on what error to return. In any case, I think it makes more sense for it to be consistent with the email path, ie. using a dialog. * Avoid nested forms * Snapshots * More snapshots * Test the hs side * Snapshots * Test IS bind/revoke * Test remove can be cancelled * Test unvalidated cases & fix phone error * Reset state between tests * Import useState directly * One more direct React import
2024-08-14 21:13:57 +08:00
.mx_EmailAddressesPhoneNumbers_verify {
display: flex;
}
.mx_EmailAddressesPhoneNumbers_existing_button {
justify-content: right;
}
.mx_EmailAddressesPhoneNumbers_verify_instructions {
flex: 1;
}
Reference in New Issue Copy Permalink