spell checking support for input fields in the browser like issue-title? #106590

bvarwig · 2024-02-07T08:09:28Z

bvarwig
Feb 7, 2024

Select Topic Area

Product Feedback

Body

As a dyslexic, I have spell-checking turned on in my browser. This works fine for many input fields. But for some, such as the title of an issue, it does not work, and I often forget to do an "external" spellcheck in another tool.

You could do dyslexics a great favour by enabling spell-checking for all input files. Do I need to open an Issue? If so, can someone show me how?

Answered by bvarwig

Jul 30, 2024

Thanks for investigating :-)

After checking, disabling various extensions and reinstalling the Grammarly extension, I now also have spell checking for titles :-)

support ticket open for Grammarly: https://support.grammarly.com/hc/en-us/requests/6797409

Regards Britta

View full answer

cehfisher · 2024-05-28T18:24:40Z

cehfisher
May 28, 2024

Hello @bvarwig - thank you for providing this feedback! We will file this with our Accessibility team so that it can be reviewed and will follow-up here with any additional questions or updates. Thanks again!

0 replies

ericwbailey · 2024-07-26T20:40:00Z

ericwbailey
Jul 26, 2024

Hi @bvarwig, thank you for reporting this. I'm a member of the accessibility team, and I'll be investigating this issue.

I did an initial investigation of editing Issue and Pull Request titles, both with creating new ones and editing existing ones. I was able to reproduce spellcheck error indication for Blink, WebKit, and Gecko-based browsers on macOS by introducing a purposefully misspelled word into the input field.

Could you provide me information with which browser and operating system you're experiencing this in? That may help with my ability to address this issue. Thank you!

0 replies

bvarwig · 2024-07-29T07:06:30Z

bvarwig
Jul 29, 2024
Author

Helle @ericwbailey
I can reproduce this with Chrom Version 126.0.6478.183 (Official Build) (64-bit)
I am a Windows user.

Here a screenshot from this Issue which has no spell-checking even if there is an error (Chrom browser):

and here screenshot from this comment where spell-checking is forking fine (Chrom browser):

I also checked with Microsoft Edge and found out that here spell checking works fine:

Hope you have an idea of what could be the root cause of this behavior.

If you have more questions let me know and i will try to help.

Regards Britta

1 reply

ericwbailey Jul 29, 2024

Thank you for providing those annotated screenshots, @bvarwig. It's really helpful.

I have a Windows device I use for testing purposes and audited input fields for new and existing Issues, Pull Requests, and our web commit modal. Screenshots follow of what I experienced.

I tried editing in Blink-based browsers (Edge and Chrome), and also a Gecko-based browser (Firefox), using the latest version of each as well as the latest version of Windows 11. I also used private windows which do not have any browser extensions running:

🖼 Edge, Windows 11

New issue

Screenshot of a new GitHub Issue with a title that reads, 'This is a test of an Issue title with a purposely missspelllllled word'. The word 'missspelllllled' is underlined with a wavy red line, indicating that it is misspelled.

Screenshot of a new GitHub Issue with a comment that reads, 'This is a test of an Issue comment with a purposely missspelled word'. The word 'missspelllllled' is underlined with a wavy red line, indicating that it is misspelled.

Existing issue

Screenshot of an existing GitHub issue with a title that reads, 'This is a test of an edited Issue title with a purposely misspelllled word'. The word 'missspelllllled' is underlined with a wavy red line, indicating that it is misspelled.

Screenshot of an existing GitHub issue with a comment that reads, 'This is a test of an edited Issue comment with a purposely missspelllled word'. The word 'missspelllllled' is underlined with a wavy red line, indicating that it is misspelled.

New PR

Screenshot of a new GitHub PR with a title that reads, 'This is a test of an PR title with a purposely missspelllllled word'. The word 'missspelllllled' is underlined with a wavy red line, indicating that it is misspelled.

Screenshot of a new GitHub PR with a comment that reads, 'This is a test of an PR comment with a purposely missspelled word'. The word 'missspelllllled' is underlined with a wavy red line, indicating that it is misspelled.

Commit editor

Screenshot of an GitHub commit modal with a comment that reads, 'Commit message with a purposely misspellled word'. The word 'missspelllllled' is underlined with a wavy red line, indicating that it is misspelled.

Screenshot of an GitHub commit modal with a comment that reads, 'Commit description with a purposely misspellled word'. The word 'missspelllllled' is underlined with a wavy red line, indicating that it is misspelled.

Existing PR

Screenshot of an existing GitHub PR with a title that reads, 'This is a test of an edited PR title with a purposely misspelllled word'. The word 'missspelllllled' is underlined with a wavy red line, indicating that it is misspelled.

Screenshot of an existing GitHub PR with a comment that reads, 'This is a test of an edited PR comment with a purposely misspelllled word'. The word 'missspelllllled' is underlined with a wavy red line, indicating that it is misspelled.

🖼 Firefox, Windows 11

New issue

Screenshot of a new GitHub Issue with a title and comment. The title reads, 'This is a test of an Issue title with a purposely missspelllllled word'. The comment reads, 'This is a test of an Issue comment with a purposely missspelllllled word'. The word 'missspelllllled' is underlined with a wavy red line, indicating that it is misspelled.

Existing issue

Screenshot of an existing GitHub Issue with a title and comment. The title reads, 'This is a test of an edited Issue title with a purposely missspelllllled word'. The comment reads, 'This is a test of an edited Issue comment with a purposely missspelllllled word'. The word 'missspelllllled' is underlined with a wavy red line, indicating that it is misspelled.

New PR

Screenshot of a new GitHub PR with a title and comment. The title reads, 'This is a test of a PR title with a purposely missspelllllled word'. The comment reads, 'This is a test of a PR comment with a purposely missspelllllled word'. The word 'missspelllllled' is underlined with a wavy red line, indicating that it is misspelled.

Commit editor

Screenshot of an GitHub commit modal with a comment and an extended description. The comment reads, 'Commit message with a purposely misspellled word'. The extended description reads, 'Commit description with a purposely missspelllled word'. The word 'missspelllllled' is underlined with a wavy red line, indicating that it is misspelled.

Existing PR

Screenshot of an existing GitHub PR with a title and comment. The title reads, 'This is a test of an edited PR title with a purposely missspelllllled word'. The comment reads, 'This is a test of an edited PR comment with a purposely missspelllllled word'. The word 'missspelllllled' is underlined with a wavy red line, indicating that it is misspelled.

🖼 Chrome, Windows 11

New issue

Existing issue

New PR

Commit editor

Existing PR

To me, this signals that it may be an issue with Grammarly, or another extension you have installed. They sometimes modify the underlying attributes on web inputs, including removing spellchecking hints.

One thing you could try to narrow down the problem space is attempting to edit an Issue in a Chrome private window on your end of things and see if the lack of spellchecking problem persists.

If it turns out an extension is causing the issue, there is unfortunately not a lot we can do on our end of things for third party services that modify our UI. If the issue is coming from Grammarly in particular I'd suggest contacting their support to file a bug.

2024-07-29T19:36:05Z

github-actions[bot]
bot Jul 29, 2024

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

Your input will be carefully reviewed and cataloged by members of our product teams.
- Due to the high volume of submissions, we may not always be able to provide individual responses.
- Rest assured, your feedback will help chart our course for product improvements.
Other users may engage with your post, sharing their own perspectives or experiences.
GitHub staff may reach out for further clarification or insight.
- We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

Upvote and comment on other user feedback Discussions that resonate with you.
Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

0 replies

bvarwig · 2024-07-30T07:05:33Z

bvarwig
Jul 30, 2024
Author

Thanks for investigating :-)

After checking, disabling various extensions and reinstalling the Grammarly extension, I now also have spell checking for titles :-)

support ticket open for Grammarly: https://support.grammarly.com/hc/en-us/requests/6797409

Regards Britta

1 reply

ericwbailey Jul 30, 2024

That's great news! I have a few friends who also use Grammarly for Dyslexia and other conditions, so it's great to know there's a solution here. Thanks for sharing the update 🙂

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

GitHub Community

spell checking support for input fields in the browser like issue-title? #106590

{{title}}

Replies: 5 comments 2 replies

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

New issue

Existing issue

New PR

Commit editor

Existing PR

New issue

Existing issue

New PR

Commit editor

Existing PR

New issue

Existing issue

New PR

Commit editor

Existing PR

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

Select a reply

GitHub Community

spell checking support for input fields in the browser like issue-title? #106590

bvarwig Feb 7, 2024

Select Topic Area

Body

Replies: 5 comments · 2 replies

cehfisher May 28, 2024

ericwbailey Jul 26, 2024

bvarwig Jul 29, 2024 Author

ericwbailey Jul 29, 2024

New issue

Existing issue

New PR

Commit editor

Existing PR

New issue

Existing issue

New PR

Commit editor

Existing PR

New issue

Existing issue

New PR

Commit editor

Existing PR

github-actions[bot] bot Jul 29, 2024

bvarwig Jul 30, 2024 Author

ericwbailey Jul 30, 2024

bvarwig
Feb 7, 2024

Replies: 5 comments 2 replies

cehfisher
May 28, 2024

ericwbailey
Jul 26, 2024

bvarwig
Jul 29, 2024
Author

github-actions[bot]
bot Jul 29, 2024

bvarwig
Jul 30, 2024
Author