Closed
Bug 31094
Opened 25 years ago
Closed 12 years ago
Unable to click when opening a invalid in composer adress from the Open Web location under the file menu
Categories
(SeaMonkey :: Composer, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: ccroft, Unassigned)
References
()
Details
From Bugzilla Helper: User-Agent: Mozilla/4.72 [en] (Win98; I) BuildID: 2000022820 I go into the composer (editor) program and click the Open Web Page Location under the file menu and if the web page adress is invalid you wont be able to click any where except another window. Reproducible: Always Steps to Reproduce: 1.Open the Composer Program 2.Click Open Page Location under the file menu 3.enter an invalid adress and click Open 4.Click OK Actual Results: You where unable to click or select anything in that window Expected Results: Automaticly closed the Open Page Location or have it as an active window
Comment 1•24 years ago
|
||
in the build from 6 APR, when an invalid address is entered, an error dialog box is displayed requiring user confirmation. This is working as designed. If this can be reproduced using a current build, please reopen and describe in detail the actions taken to reproduce this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
I still see problems. 1) launch netscape 2) launch composer 3) File | Open Web Page location 4) enter invalid URL, click OK 5) click OK on error panel now I can't use composer window at all.... I can reproduce this...composer window doesn't regain control after the invalid URL detect.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Comment 5•24 years ago
|
||
sujay -- what platform are you testing on, I can not repro this on windows
Comment 7•24 years ago
|
||
after watching what Sujay did to reproduce this, it seems more like a netlib issue. When the alert box comes up that states the location cannot be found -- the app seems to continue to cycle indefinitely. assigning this to netlib so they can take a look at it
Component: Editor → Networking
Target Milestone: M17 → ---
Comment 8•24 years ago
|
||
reassign to component owner
Assignee: brade → gagan
QA Contact: sujay → tever
Comment 9•24 years ago
|
||
confirming bug to get it out of the unconfirmed list. Sorry for the spamm
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 10•24 years ago
|
||
we are correctly firing the OnStop but I think the request is not being pulled out of the loadgroup or something on the webshell. ruslan can you investigate?
Assignee: gagan → ruslan
Comment 11•24 years ago
|
||
mscott: this looks like a uriloader problem. In the onStopRequest of the nsDocLoader seem to walk differently between the composer and the navigator. And that results in the logo continuing to spin. Could you take a look at this? thx. (gagan from ruslan's desk)
Assignee: ruslan → mscott
Updated•24 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → M17
Comment 12•24 years ago
|
||
adding relnote keyword since this might confuse some users who make inadvertent typos.
Keywords: relnote
Comment 13•24 years ago
|
||
I'm not seeing this. I get a vague "unable to edit this type of page" message for a bogus hostname (and am taken back to the page I was last editing), and I can edit a 404 page. I don't this bug was fixed in bug 55750 because I don't see the problem in a 1002 build either.
Comment 14•24 years ago
|
||
> and am taken back to the page I was last editing Oops, and the window closes. I didn't notice it was opening in a *new* composer window because of bug 34930 (which is mysteriously marked "invalid").
Comment 15•24 years ago
|
||
This seems to be working now, so: It seems unclear to me whether this bug requires either of a "developer" or "user" release note for Netscape 6 RTM. If anyone feels it does, can they please draft one and then nominate with the relnote-user or relnote-devel strings in the Status Whiteboard. Thanks :-) Gerv
Comment 16•24 years ago
|
||
(Addendum to previous comment: I've found this on the Linux build, running on RedHat 7.0)
Updated•24 years ago
|
Target Milestone: M17 → ---
Comment 18•23 years ago
|
||
Sounds like another component that does not get back connection failures from Necko. I'm marking as depends on 19073, anyone who understands the internals can remove this if I am off-base.
Depends on: 19073
Comment 19•23 years ago
|
||
is this worth release noting? I'm going to ignore it on my first pass of writing...
Comment 20•21 years ago
|
||
this sounds familiar. cvs build from no more than a week ago: steps: 1. file>open web location 2. unknown-p:foo 3. open in: new composer window 4. open 5. find and dismiss the alert (see 4b') expected results: i'm not sure :) actual results: 4a' a composer window opens (somewhere, it doesn't appear in the foreground, but it is in the window list) 4b' an alert opens complaining about my location (this is semi reasonable although not ideal) (it too isn't in the foreground, but it unlike composer will come to front if you select it from the window list) 5' the composer window is almost entirely unusable, you can close it with the system close widgets. i'm trouncing this bug to editor to get it retriaged because it's such an old bug. i suspect there's a dupe or two lying around somewhere.
Assignee: mscott → composer
Status: ASSIGNED → NEW
Component: Networking → Editor: Composer
Keywords: qawanted
Comment 21•21 years ago
|
||
-> qa.
Updated•20 years ago
|
Product: Browser → Seamonkey
Comment 22•19 years ago
|
||
not a dupe
Keywords: qawanted
Summary: Unable to click when opening a invalid adress from the Open Web location under the file menu → Unable to click when opening a invalid in composer adress from the Open Web location under the file menu
Updated•16 years ago
|
Assignee: composer → nobody
Priority: P3 → --
QA Contact: nobody → composer
Comment 23•12 years ago
|
||
WMF, no window/browser lock when opening incorrect address User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/16.0 Firefox/16.0 SeaMonkey/2.13a1 Build identifier: 20120712003002
Status: NEW → RESOLVED
Closed: 24 years ago → 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•