Closed
Bug 8552
Opened 26 years ago
Closed 26 years ago
translation of the bugzilla page wont work - crash
Categories
(Core :: Networking, defect, P3)
Tracking
()
VERIFIED
FIXED
People
(Reporter: csbooton, Assigned: warrensomebody)
References
()
Details
To reproduce this (Im using the 1999061808 build) Go to the bugzilla main page and click on translate>english to (any of the three) and you get a message that the browser sent a message that the server could not understand. I call this a blocker as it blocks the translation of the page and there apeears no way to get past it.
I went to http://bugzilla.mozilla.org/ and do not see a translate>english
selection...please give me more details or I will have to make this Invalid.
Comment 2•26 years ago
|
||
I am fairly sure that he refers to is View -> Translate -> English to _____. You
can also access it on the main toolbar.
The Alis server responds with an error 400. I've looked at the source of the
bugzilla page versus the source of other pages, and cannot determine why it
returns this error.
Component: other → Bugzilla
Product: Browser → Webtools
QA Contact: leger → csbooton
Updated•26 years ago
|
Assignee: terry → chofmann
Component: Bugzilla → other
Product: Webtools → Browser
QA Contact: csbooton → leger
Comment 4•26 years ago
|
||
This has nothing to do with Bugzilla; it just seems that the bugzilla main
page is an interesting test case for this translation feature (about which
I know nothing.)
Moving back to Browser/other, which seemed like a fine starting place.
Updated•26 years ago
|
Assignee: chofmann → karnaze
Summary: translation of the bugzilla page wont work → translation of the bugzilla page wont work - crash
Comment 5•26 years ago
|
||
in latest builds on win32 I crash when hit translate on bugzilla.
so we might be blocked on investigating until the crash is fixed.
I also hit the translate crash on other pages like www.mozilla.org
Incident ID 11315637
nsFrameImageLoader::DamageRepairFrames
[d:\builds\seamonkey\mozilla\layout\base\src\nsFrameImageLoader.cpp, line 578]
nsFrameImageLoader::Notify
[d:\builds\seamonkey\mozilla\layout\base\src\nsFrameImageLoader.cpp, line 460]
ns_observer_proc [d:\builds\seamonkey\mozilla\gfx\src\nsImageRequest.cpp, line
126]
XP_NotifyObservers [d:\builds\seamonkey\mozilla\modules\libutil\src\obs.c, line
260]
il_pixmap_update_notify [d:\builds\seamonkey\mozilla\modules\libimg\src\if.cpp,
line 311]
il_flush_image_data [d:\builds\seamonkey\mozilla\modules\libimg\src\scale.cpp,
line 216]
ImgDCallbk::ImgDCBFlushImage
[d:\builds\seamonkey\mozilla\modules\libimg\src\if.cpp, line 170]
il_gif_write [d:\builds\seamonkey\mozilla\modules\libimg\gifcom\gif.cpp, line
1429]
GIFDecoder::ImgDWrite
[d:\builds\seamonkey\mozilla\modules\libimg\gifcom\nsGIFDecoder.cpp, line 284]
IL_StreamWrite [d:\builds\seamonkey\mozilla\modules\libimg\src\if.cpp, line 985]
NetReaderImpl::Write
[d:\builds\seamonkey\mozilla\modules\libimg\src\ilNetReader.cpp, line 95]
ImageConsumer::OnDataAvailable
[d:\builds\seamonkey\mozilla\gfx\src\nsImageNetContextAsync.cpp, line 295]
nsDocumentBindInfo::OnDataAvailable
[d:\builds\seamonkey\mozilla\webshell\src\nsDocLoader.cpp, line 2025]
OnDataAvailableProxyEvent::HandleEvent
[d:\builds\seamonkey\mozilla\network\module\nsNetThread.cpp, line 634]
StreamListenerProxyEvent::HandlePLEvent
[d:\builds\seamonkey\mozilla\network\module\nsNetThread.cpp, line 474]
PL_HandleEvent [plevent.c, line 510]
PL_ProcessPendingEvents [plevent.c, line 471]
_md_EventReceiverProc [plevent.c, line 936]
KERNEL32.DLL + 0x3663 (0xbff73663)
KERNEL32.DLL + 0x22894 (0xbff92894)
0x00638c1c
Updated•26 years ago
|
Assignee: karnaze → warren
Comment 6•26 years ago
|
||
This stack doesn't have tables in it. Reassigning to Warren.
Comment 8•26 years ago
|
||
I don't see this being a necko issue, nor do I see a crash on 8/9 builds. Is
this an issue for the i18n group?
| Assignee | ||
Comment 9•26 years ago
|
||
The stack points to a layout problem, not necko. But then you said it doesn't
crash anymore. What's the problem?
Updated•26 years ago
|
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Comment 10•26 years ago
|
||
I think the problem is that the translate doesn't do anything, obviously not a
necko issue. Marking this bug resolved fixed, which dealt with a crash.
Please open a new bug if the functionality of the translate menu item is
incorrect and give it to the internationaliztion component.
Comment 11•26 years ago
|
||
If the translate button is not working. then we need to get Marketing
people involved. CC'ing roberts and chrisn.
Comment 12•26 years ago
|
||
roberts@ns and chrisn@ns do not seem to be registered with Bugzilla.
Will send a note to them as a reminder.
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
Comment 13•26 years ago
|
||
the crash is gone marking verified, I don't know what is up with the
functionality of the translate menu, please open a new one for that
Comment 14•26 years ago
|
||
Isn't the original failure to translate covered under this bug? I won't reopen,
though.
Comment 15•26 years ago
|
||
Bulk move of all Necko (to be deleted component) bugs to new Networking
component.
You need to log in
before you can comment on or make changes to this bug.
Description
•