Closed Bug 74680 Opened 24 years ago Closed 9 years ago

Choosing the same charset as the webpage is already presented in shouldn't reload the page

Categories

(Core :: Internationalization, defect, P4)

defect

Tracking

()

RESOLVED WONTFIX
Future

People

(Reporter: bugzilla, Assigned: nhottanscp)

References

()

Details

(Keywords: intl)

Attachments

(2 files)

If you go to: http://contactel.sprawl.dk/ and check the View -> Char Code it's set to Centrael Europe If the user selects View -> Char Code -> Centrael Europe Mozilla shouldn't reload the page
Reassign to jbetak.
Assignee: nhotta → jbetak
accepting
Status: NEW → ASSIGNED
Priority: -- → P4
Target Milestone: --- → mozilla0.9.1
QA Contact: andreasb → ylong
Naoki, could you please help me with yet another review? It's virtually the same stuff like in bug 60406. I was somewhat concerned about performance, but this only gets executed, when manually overriding a charset, not when e.g. reloading a page. I think we should be fine...
Keywords: intl
Did you test with many cases (META, HTTP server, frame, etc.)? I think we do not need to fix this unless we are sure about no regression with the patch.
Naoki, I did fair amount of testing and I'm quite certain about the implications. This event handler gets executed only when there is manual user interaction in the Charset Menu. Basically it's just for charset override. It would also give Mozilla an edge over IE, since they do a reload when you try to override the current charset with the same thing manually.
But please test with frame cases where a page contains multiple frames in different charsets. Make sure you do not use a parent charset when the user is trying to change a charset of a particular frame.
will do. BTW do we have a set of test pages somewhere? Am I correct in assuming that frame-specific override will be achieved via the context (right-mouse- button) menu?
reassign to nhotta
Assignee: jbetak → nhotta
Status: ASSIGNED → NEW
I realized that that's not implemented (bug 63054). So no way to test. The patch looks fine but I am not comfortable checking in now, and the reload issue is not critical for 0.9.1.
Status: NEW → ASSIGNED
Target Milestone: mozilla0.9.1 → Future
this really must be easy to fix. Something about: newcharset != oldcharset then reload()
QA Contact: amyy → i18n
Telemetry shows that this feature is used extremely rarely. It is not worthwhile to polish this feature further.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: