Closed
Bug 338553
Opened 18 years ago
Closed 16 years ago
Epson technical e-talk will not accept messages
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: michael.graubart7, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.4) Gecko/20060508 SeaMonkey/1.0.2 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.4) Gecko/20060508 SeaMonkey/1.0.2 This is a direct e-talk question-and-answer method of communicating with an Epson technician about problems. Using Safari, one connects to the site, which opens a window showing Epson's response and, in due course, allows one to type one's own responses into a window at the bottom of the page. In SeaMonkey 1.0.2 one either gets no further at all after clicking 'Go', or one is sent a file called 'srvgate.dll' file for downloading, which seems to be empty. Reproducible: Always Steps to Reproduce: 1. Go to http://etalk.epson.co.uk/ 2. Select a type of appliance; type in own name and e-address, and a brief technical query. 3. Click 'GO'. Actual Results: Either nothing, or one is invited to open or download 'srvgate.dll'. The latter turns out to be empty. Expected Results: A window should open, with messages from Epson and an indication of where one is in the queue. Eventually a response from an Epson technician appears, allowing one to reply in a window at the foot of the page — and so on. eMac PPC G4, OS X 10.4.6, Classic theme.
Comment 1•18 years ago
|
||
*** Bug 341619 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 2•17 years ago
|
||
The behaviour of this website when using SeaMonkey 1.1 is different: when one reaches the opening page and clicks 'Go', a page headed with 'EPSON e-Talk is currently closed' appears, listing the opening hours and days. (With FireFox, behaviour is as described for SeaMonkey 1.0.2 above.) If one uses Safari, the site behaves correctly.
Reporter | ||
Comment 3•17 years ago
|
||
Bug still present in trunk and 1.1.2 builds.
Comment 4•16 years ago
|
||
The URL gives a 404 now.
Updated•16 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•