Closed Bug 1604145 Opened 5 years ago Closed 5 years ago

No way to (re-)enable Japanese detector

Categories

(Core :: Internationalization, defect)

defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: emk, Unassigned)

References

(Regression)

Details

(Keywords: regression)

Bug 1543077 removed "Japanese" from "Auto-Detect" section of the Text Encoding menu. It might be okay, but I noticed that it does not provide another way to enable Japanese detector. Although Japanese localization enables Japanese detector by default, once I selected a menu item under "Auto-Detect" section, I can't re-enable Japanese detector anymore (unless resetting the intl.charset.detector pref from about:config).

I propose moving "Japanese" to "Auto-Detect" section because "Japanese" menu item is actually doing auto-detect and it will resolve the above issue naturally.

I can't re-enable Japanese detector anymore

It's supposed to be unconditionally enabled regardless of what intl.charset.detector says. Is there a case where it's supposed to run but isn't running?

Prior to last Friday's Nightly, the Auto-Detect submenu was supposed to control only the Cyrillic detector without affecting the Japanese one. Starting with last Friday's Nightly, the Auto-Detect submenu is supposed to no longer show up at all.

Needinfoing for "Is there a case where it's supposed to run but isn't running?"

Flags: needinfo?(VYV03354)

(In reply to Henri Sivonen (:hsivonen) from comment #1)

It's supposed to be unconditionally enabled regardless of what intl.charset.detector says. Is there a case where it's supposed to run but isn't running?

You are right. I'm confusing somehow.

Starting with last Friday's Nightly, the Auto-Detect submenu is supposed to no longer show up at all.

I still see "Auto-Detect" section regardless of the intl.charset.detector.ng.enabled value. I'll file another bug.

Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(VYV03354)
Resolution: --- → INVALID
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.