Closed
Bug 25535
Opened 25 years ago
Closed 25 years ago
[PP] This page is not loaded in Linux
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
VERIFIED
WORKSFORME
M14
People
(Reporter: teruko, Assigned: travis)
References
()
Details
(Whiteboard: [PDT+])
When you go to the page, "Transferring data from chinese.china.com" is displayed in the status bar.
I waited for a while, but nothing is displayed.
Steps of reproduce
1. Go to above URL
This is reproduciable in 1-27-09 and 1-28-08 M14 Linux build.
This does not happen in 1-25-20 M13 Linux build.
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M14
Comment 1•25 years ago
|
||
I found one problem and assign a new bug to vidur. Bug 26236. Howerver, that is
not the only problem. We still do not display even after I fix that in my local
build.
I down load that page and modified it. It show me correctly after I comment out
the line popup = window.open in it's JavaScript code
If I do not comment out that line, nothing will show and a warning message
"we don't handle eBorderStyle_close yet. pleae fix me" show in the stderr
Reassign this to blizzard because the cvsblame show him in that printf line.
Also cc vidur since it is an issue in the window.open.
Change component from Internationaliztion to DOM Level 0
Assignee: ftang → blizzard
Status: ASSIGNED → NEW
Component: Internationalization → DOM Level 0
Comment 2•25 years ago
|
||
That's just a warning that says that we don't support windows without borders
yet, it's just a decoration problem. I might have touched that line but I
didn't write it. :)
Anyway, I don't think that this is a window issue. You might want to reassign
this to someone who can track it down.
Putting on PDT+ radar for beta1. Moving over to vidur per rickg's request.
Assignee: blizzard → vidur
Whiteboard: [PDT+]
Comment 4•25 years ago
|
||
The unescape problem described in bug 26236 has been fixed. The window.open
problem is described in bug 26129. DUPing this bug with the latter.
*** This bug has been marked as a duplicate of 26129 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 5•25 years ago
|
||
26129 was fixed, but Mozilla crashed when I tested this in 2000020809 Linux build.
Talkback Incident 5084153
Trigger Type: Program Crash
Trigger Reason: SIGSEGV: Segmentation Fault: (signal 11)
Call Stack: (Signature = nsURILoader::ShouldHandleContent() 6f18cf01)
nsURILoader::ShouldHandleContent()
nsURILoader::DispatchContent()
nsDocumentOpenInfo::DispatchContent()
nsDocumentOpenInfo::OnStartRequest()
nsCachedChromeChannel::AsyncRead()
nsDocumentOpenInfo::Open()
nsURILoader::OpenURIVia()
nsURILoader::OpenURI()
nsWebShell::DoLoadURL()
nsWebShell::LoadURI()
nsWebShell::LoadURL()
nsWebShell::LoadURL()
nsWebShellWindow::Initialize()
nsAppShellService::JustCreateTopWindow()
nsAppShellService::CreateTopLevelWindow()
nsXULWindow::CreateNewContentWindow()
nsXULWindow::GetNewWindow()
nsContentTreeOwner::GetNewWindow()
GlobalWindowImpl::OpenInternal()
GlobalWindowImpl::Open()
WindowOpen()
js_Invoke()
js_Interpret()
js_Execute()
JS_EvaluateUCScriptForPrincipals()
nsJSContext::EvaluateString()
HTMLContentSink::EvaluateScript()
HTMLContentSink::ProcessSCRIPTTag()
HTMLContentSink::AddLeaf()
CNavDTD::AddLeaf()
CNavDTD::HandleScriptToken()
CNavDTD::OpenContainer()
CNavDTD::HandleDefaultStartToken()
CNavDTD::HandleStartToken()
CNavDTD::HandleToken()
CNavDTD::BuildModel()
nsParser::BuildModel()
nsParser::ResumeParse()
nsParser::OnDataAvailable()
nsDocumentOpenInfo::OnDataAvailable()
nsHTTPResponseListener::OnDataAvailable()
nsOnDataAvailableEvent::HandleEvent()
nsStreamListenerEvent::HandlePLEvent()
PL_HandleEvent()
PL_ProcessPendingEvents()
nsEventQueueImpl::ProcessPendingEvents()
event_processor_callback()
our_gdk_io_invoke()
libglib-1.2.so.0 + 0xe52a (0x406a452a)
libglib-1.2.so.0 + 0xfbe6 (0x406a5be6)
libglib-1.2.so.0 + 0x101a1 (0x406a61a1)
libglib-1.2.so.0 + 0x10341 (0x406a6341)
libgtk-1.2.so.0 + 0x8c209 (0x405cd209)
nsAppShell::Run()
nsAppShellService::Run()
main1()
main()
libc.so.6 + 0x181eb (0x4021e1eb)
I need to reopen this.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 6•25 years ago
|
||
The problem on the 2/8 build was probably a result of Travis's change. He and
mscott supposedly fixed it. Handing it over to Travis to confirm that it's
fixed. This is no longer my bug.
Assignee: vidur → travis
Status: REOPENED → NEW
Reporter | ||
Comment 7•25 years ago
|
||
Crash does not happen in 20000908 Linux build. I mark this as Worksforme.
Status: NEW → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → WORKSFORME
This was fixed with yeseterday's fixes, this was actually a dup of another bug
that was a tree stopper yesterday.
Reporter | ||
Comment 9•25 years ago
|
||
I verified this in 2000021008 Linux build.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•