Skip to content

fix: correct label htmlFor attributes in AccountForm#4010

Closed
ashuverma25 wants to merge 81 commits intoprocessing:developfrom
ashuverma25:fix-account-form-a11y
Closed

fix: correct label htmlFor attributes in AccountForm#4010
ashuverma25 wants to merge 81 commits intoprocessing:developfrom
ashuverma25:fix-account-form-a11y

Conversation

@ashuverma25
Copy link
Copy Markdown

What this PR does:
This fixes the accessibility bug reported in #3945. The htmlFor attributes in AccountForm.tsx contained spaces (current password and new password) and did not match the actual input IDs.

I updated the labels to use camelCase (currentPassword and newPassword) to perfectly match the input fields, ensuring screen readers can correctly associate the labels with the inputs.

khanniie and others added 30 commits January 24, 2025 00:15
…ersion-hint-file

Editor file splitting: create new hint file
…ersion-utils-tidy

Moves the tidier code and file mode utils out of editor file
I'm fairly certain that we can remove ```
      if (!prevProps?.unsavedChanges) {
        setTimeout(() => setUnsavedChanges(false), 400);
      }
```

I looked at the git blame and it looks like the intention was to stop setting unsavedchanges to false when the files switched, but i think the solve that was implemented 9 years ago did something like "if c == false, c = false" and we should be able to safely remove it instead.

reference commit: processing@77e2f5b
…ersion-splitoff-codemirror

Convert Editor to functional, splits off CodeMirror code into its own file
khanniie and others added 26 commits January 6, 2026 10:03
…or-v6

Convert tidier.js to TypeScript && test coverage of tidier.ts
@yugalkaushik
Copy link
Copy Markdown
Contributor

@ashuverma25 Thank you for the PR. It quite hard to review and does not seem well structured. Can you please check it out yourself once.

@ashuverma25
Copy link
Copy Markdown
Author

@ashuverma25 Thank you for the PR. It quite hard to review and does not seem well structured. Can you please check it out yourself once.

@yugalkaushik I have closed this PR and opened a fresh one here: #4011 . This new PR has a clean history with only 1 commit and no conflicts. Sorry for the messy history earlier!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants