Closed Bug 292188 Opened 20 years ago Closed 19 years ago

first digit returned by cuecat scanner w/yourcat driver truncated

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: byoungdt, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

When scanning a UPC with a cue cat using the yourcuecat 1.91 driver into a text
box, search box or URL box the leading digit is always truncated. This behavior
is not exhibited by IE 6.0 and it behaves normally returning all digits.

Reproducible: Always

Steps to Reproduce:
1.install cuecat and driver
2.select text box or other data entry field
3.scan barcode

Actual Results:  
First digit of barcode is always truncated

Expected Results:  
all digits should have appeared in the text box

Even though the cuecat is no longer produced many PC and linux users use the
cuecat to scan ISBNS and UPCs. Websites including google, yahoo search, amazona
and eBay are now offering searches based on this data. CueCats are the perfect
low cost solution. To see the popularity search eBay for cuecats. Internet
explorer handles the input whereas Mozilla does not
Digital Convergence who made the CueCat went bust in January 2002. From what I
read in many places online, their driver software is spyware.

I'd advise you buy a proper barcode reader (preferably with keyboard wedge or
USB) or type the UPC code yourself - it is only 12 or 13 digits.

Invalid?
The new driver is open source not the original. The use of cucat with this OS 
driver is very common.....
Mozilla.org does not produce anything related to the CueCat that I'm aware of.  
So what is the bug about?  If it's about rendering some particular HTML page
that the cuecat driver produces, please attach said page to the bug using
https://bugzilla.mozilla.org/attachment.cgi?bugid=292188&action=enter
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.