267428 - message/rfc822 ignores UTF-8 encoding and javascript in html to place focus

Status: RESOLVED EXPIRED

(Core :: Internationalization, defect)

Description

[Ralf Hauser]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5) Gecko/20041024
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5) Gecko/20041024

see the mht attachment of Bug 267427 (as per the above URL)

related is probably Bug 161715

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Actual Results:  
iso8859-1

Expected Results:  
utf-8 (manually this can be fixed afterwards, but if the input properly
specifies the encoding, one would expect mozilla to honor it)

Comment 1

[Ralf Hauser]

obviously, MSIE handles its own mht archives properly, but also when renaming it
to .eml, OutlookExpress does a good job

Comment 2

[OstGote!]

For the incorrect display of EML and message/rfc822 in the browser see Bug
206421 and Bug 56908.

Comment 3

[Boris Zbarsky [:bzbarsky]]

Marking invalid due to lack of steps to reproduce, which makes it impossible to
do anything with this bug.  Please feel free to reopen when you provide the
steps to reproduce.

Comment 4

[Ralf Hauser]

Boris, do you need an attachment uploaded for each bug again (no hyperlink
possible?)

Steps to reproduce:
1) open the attachment
2 [details] [diff] [review]) put the focus in the "to" field (tabindex=1)
3) tab through the fields
4) notice that the cursor doesn't jump from tabindex 2 to tabindex 3, but does
an extra step

Comment 5

[Ralf Hauser]

ooops - the steps I gave were for the original problem:

For here (encoding):
1) open the attachment as per the above URL
2) change the encoding from iso8859-1 to UTF and the TM (trademark) in the
top-left link or the (c) (copyright) sign at the bottom-right will all of a
sudden display correctly.

JavaScript-tabindex
1) open the attachment
2 [details] [diff] [review]) the focus is placed correctly on the to field, but tabindex is entirely
ignored when using the TAB key
3) when placing the focus with the mouse again in the to fields and then TABing,
tabindexes are honoured with the flaw as reported in Bug 267427

Comment 6

[Boris Zbarsky [:bzbarsky]]

(In reply to comment #4)
> Boris, do you need an attachment uploaded for each bug again (no hyperlink
> possible?)

No.  What I want are clear instructions on how to reproduce the bug, with a
clear description of the expected and actual results.  Note that _you_ couldn't
easily tell what this bug was about, and you filed it.  Given a choice between
working on a bug that is clearly described and reproducible and one where I have
to try to guess what the reporter meant, it's a no-brainer.  The latter will
thus never get worked on, for there's no shortage of the former.

(In reply to comment #5)
> For here (encoding):
> 1) open the attachment as per the above URL
> 2) change the encoding from iso8859-1 to UTF and the TM (trademark) in the
> top-left link or the (c) (copyright) sign at the bottom-right will all of a
> sudden display correctly.

When I load the attachment in a current trunk build (2004-11-08-05, to be
precise), with charset autodetect off, it loads a UTF-8.  The "TM" and "(c)"
show up correctly.

> JavaScript-tabindex

This sounds like a separate bug from the encoding thing, no?  Please file one
bug per issue.

Comment 7

[Ralf Hauser]

build 2004111305 with autodetect off on WinXP attempts to load it as iso8859-1
instead of UTF-8

Sorry for not filing a separate bug on the "focus" issue that it places the
cursor right, but apparently doesn't initialize the tabindex properly

Comment 8

[Boris Zbarsky [:bzbarsky]]

Doesn't sound like a layout bug.  Over to intl.

Comment 9

[Gervase Markham [:gerv]]

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/

Comment 10

[Gervase Markham [:gerv]]

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.