Join us to show up for other Firefox users 🦊. Earn fun badges and Mozilla swag vouchers! Find out more: https://mzl.la/askafox150

Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Əgər kömək lazımdırsa lütfən yeni sual verin.

Firefox is not recognizing FNC character coming from the input stream

  • 4 cavab
  • 0 have this problem
  • 142 views
  • Last reply by Mike Kaply
  • Həll olunub

Alpesh Sanghvi
Alpesh Sanghvi

We are allowing end user to scan 2D matrix barcode using a wedge scanner in our application. We are facing a problem where different elements of the bar code are not getting split into the application. On investigating this further, we found that Firefox browser not recognising the FNC character(input character 29) coming from input stream (barcode scanner in this case).

We are allowing end user to scan 2D matrix barcode using a wedge scanner in our application. We are facing a problem where different elements of the bar code are not getting split into the application. On investigating this further, we found that Firefox browser not recognising the FNC character(input character 29) coming from input stream (barcode scanner in this case).
Attached screenshots

Chosen solution

Bug 1990303 has been raised on bugzilla

Read this answer in context 👍 0

All Replies (4)

TyDraniu
TyDraniu
  • Top 10 Contributor

Hi, I think it would be better to report it at https://bugzilla.mozilla.org.

You could mention there that it works in other browsers.

Mike Kaply
Mike Kaply
  • Moderator
Mozilla Staff

And please post the bug number when you do so.

Alpesh Sanghvi
Alpesh Sanghvi Question owner

Seçilmiş Həll

Bug 1990303 has been raised on bugzilla

Mike Kaply
Mike Kaply
  • Moderator
Mozilla Staff

Thanks. I'm going to mark opening the bug as "solving the problem" since that's where we'll figure things out.