Open a GTK-based browser and load page: http://testsuite.nokia-boston.com/content/esmp_nonESMP/navigatorObject/language1.asp actual result: language translation shows "en" expected result: language translation should show "en-US" or "en-us" This bug is related to bug 29653 where the same problem reported on Qt browsers. The current LayoutTests/fast/js/navigator-language.html only checks if the two leading letters are "en". However, it should make a case insensitive check against "en-us" after GTK is fixed.
(In reply to comment #0) > Open a GTK-based browser and load page: > http://testsuite.nokia-boston.com/content/esmp_nonESMP/navigatorObject/language1.asp > actual result: language translation shows "en" > expected result: language translation should show "en-US" or "en-us" > > This bug is related to bug 29653 where the same problem reported on Qt > browsers. The current LayoutTests/fast/js/navigator-language.html only checks > if the two leading letters are "en". However, it should make a case insensitive > check against "en-us" after GTK is fixed. I think you should go ahead and check for en-us right now, since the problem in GTK+'s DRT is a bit bigger than just this. I will make this a duplicate of the other bug as you suggested =). *** This bug has been marked as a duplicate of bug 30440 ***