Search and Top Navigation
#9519 closed bug (notabug)
Opened August 27, 2013 03:16PM UTC
Closed August 27, 2013 04:43PM UTC
Firefox and i18n
| Reported by: | ghorner | Owned by: | ghorner |
|---|---|---|---|
| Priority: | minor | Milestone: | none |
| Component: | ui.datepicker | Version: | 1.10.3 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
Firefox language strings are lower case; which prevents matching the language for date picker etc.
should the language string be lower cased/case invariant during searching?
Attachments (0)
Change History (3)
Changed August 27, 2013 03:23PM UTC by comment:1
| owner: | → ghorner |
|---|---|
| status: | new → pending |
Changed August 27, 2013 04:21PM UTC by comment:2
| status: | pending → new |
|---|
when using the jquery ui i18n script to set the language/culture of the datepicker; i18n language/culture is defined as 'en-GB', 'en-US' etc.
the user browser language/culture in IE and Chrome conform to this standard; however Firefox user browser language/culture is lower cased 'en-GB' in Firefox is 'en-gb' and this prevents the selection of the correct language/culture based of the 'en-gb' supplied by Firefox.
Changed August 27, 2013 04:43PM UTC by comment:3
| component: | ui.core → ui.datepicker |
|---|---|
| resolution: | → notabug |
| status: | new → closed |
The datepicker doesn't provide an API for searching. You have to handle choosing locales on your own. So I'm not sure what you're referring to when you ask "should the language string be lower cased/case invariant during searching?" If you're trying to construct a URL to load the locale data, or if you're just loading a ton of data and then trying to set the correct one, you can easily change the casing before trying.
I have no idea what you're talking about. Please elaborate.