Active or Disabled action button in a mobile form?

I have a “change password” screen where the user’s password has expired and he/she has to change it. it’s a standard screen with “New password” and “Re-type new password” fields, with an inline validation that checks whether the password guidelines are met (while the user is typing): 8 characters, 1 digit, 1 number, 1 special character.

we have an argument whether the main “change password” action button should be disabled until all the validations are clear, or to keep it active and provide an error message if needed.

what do you think is better?

The form cannot be displayed in browser because use of session cookies has been disabled in the browser

I am new in SharePoint. I’m receiving the following error while accessing SharePoint online form using c-sharp

“The form cannot be displayed in the browser because the use of session cookies has been disabled in the current browser settings. In order to load the form, session cookies must be allowed.”

I also tried with following attempts, but did not found solution.

  1. Enabled the session cookie in the browser.

  2. Added the httpOnlyCookies tag and set to false in web.config

Thanks in Advance

Modify permissions are disabled for Global admin with full control

In Sharepoint Online, I want to restrict access to a subsite.

I have removed inheritance for the subsite and added a special group as contributors.

Now I need to remove the normal contributor group, but the button to do that “Remove User Permissions” is disabled:

enter image description here

I am Global Sharepoint admin. I am also member of the Owners group on the root site. Also, I have given Global Sharepoint admins Full control over the subsite:

enter image description here

Even on the root site, the story is the same. The Modify buttons are disabled.

Why can’t I use the Modify buttons?

Should a Save button be disabled if there have been no changes made?

I have a desktop application, and in this application there is a non-modal dialog where a user can make changes to something. The dialog has a Close button and a Save button. The Save button does not close the dialog, because we expect users to be making these changes, checking the result, and then possibly making more changes.

The state of the dialog will always be valid, there are no required fields or anything like that.

We have come up with two options for the save button:

  1. Leave the Save button enabled at all times. When a user clicks it, it will briefly display a check mark or perhaps a short success message for a couple seconds.
  2. Disable the Save button until a change has been made, then enable it. When clicked, it will go back to being disabled.

I can see pros and cons to each approach. Is there any accepted standard or a reason why one approach is better?

Physical keyboard disabled in lock screen–sometimes

I have a Dell XPS 9370 with a touch screen. When I wake it from sleep mode, but never during initial log in, sometimes the physical keyboard won’t register any input. When this happens I can still log in by swiping the screen to activate the onscreen keyboard.

Currently running Ubuntu 19.04, but have had the issue since I installed 18.04 fresh on it. Can supply any other details. Have a feeling this is something stupid but it’s driving me crazy.